Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c4dba113d33760b685cfdbc093d028adb7a9d35e0ea6fbfc5a2e3553abc2e7b4

Tx prefix hash: cc20fe46812cdb9659d0251727905ed42386c973c32f22a7e8c3b069ceb1144b
Tx public key: 7ba7509bb3e7a32e651820cc5337ed583a54ab63207adc1ded5cb22dc6c4779b
Timestamp: 1721632055 Timestamp [UCT]: 2024-07-22 07:07:35 Age [y:d:h:m:s]: 00:238:23:30:48
Block: 1071079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170715 RingCT/type: yes/0
Extra: 017ba7509bb3e7a32e651820cc5337ed583a54ab63207adc1ded5cb22dc6c4779b02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60fa61da831fe06d8edf735439a35e823a8ffb4b91fd995e305db760b698190a 0.600000000000 1543170 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1071089, "vin": [ { "gen": { "height": 1071079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60fa61da831fe06d8edf735439a35e823a8ffb4b91fd995e305db760b698190a" } } ], "extra": [ 1, 123, 167, 80, 155, 179, 231, 163, 46, 101, 24, 32, 204, 83, 55, 237, 88, 58, 84, 171, 99, 32, 122, 220, 29, 237, 92, 178, 45, 198, 196, 119, 155, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8