Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72cfe52eeeeeadb27794840654e3c8d9dbdc3300518e9b77a4d6916b28489844

Tx prefix hash: 509eaf4f556fd213a2e9449e5a613e600933d4d72ded5f3cbfa6e09f31d85e33
Tx public key: 8a4df1cd73fade2ad80125b17c828fac9ae322d3a998933c061c6e63c78a1747
Timestamp: 1733420492 Timestamp [UCT]: 2024-12-05 17:41:32 Age [y:d:h:m:s]: 00:104:02:12:14
Block: 1168719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74205 RingCT/type: yes/0
Extra: 018a4df1cd73fade2ad80125b17c828fac9ae322d3a998933c061c6e63c78a17470211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03f1711de353cd5566f88ea25f52df69407cee9d01523476e61151ad4bcc83f6 0.600000000000 1654430 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": 1168729, "vin": [ { "gen": { "height": 1168719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03f1711de353cd5566f88ea25f52df69407cee9d01523476e61151ad4bcc83f6" } } ], "extra": [ 1, 138, 77, 241, 205, 115, 250, 222, 42, 216, 1, 37, 177, 124, 130, 143, 172, 154, 227, 34, 211, 169, 152, 147, 60, 6, 28, 110, 99, 199, 138, 23, 71, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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