Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72af94fad6e0a65058d009c7695b57de26a7e840e1fb1c21910447835fd72e7f

Tx prefix hash: 9e0b1705c4fb3096e0b804c08cde3aaec2d5418fe50a75f52e09b30e0eb923e1
Tx public key: 01756096f725d115c5471b74515f17441763f60746cbfec8ce1ad1a3e8366706
Timestamp: 1707765539 Timestamp [UCT]: 2024-02-12 19:18:59 Age [y:d:h:m:s]: 00:286:03:30:54
Block: 956121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204878 RingCT/type: yes/0
Extra: 0101756096f725d115c5471b74515f17441763f60746cbfec8ce1ad1a3e836670602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc73261b33387c8dd1ecdc7c64dc5e2e7da124c84e97ea322727180fab2e8d7d 0.600000000000 1415423 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": 956131, "vin": [ { "gen": { "height": 956121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc73261b33387c8dd1ecdc7c64dc5e2e7da124c84e97ea322727180fab2e8d7d" } } ], "extra": [ 1, 1, 117, 96, 150, 247, 37, 209, 21, 197, 71, 27, 116, 81, 95, 23, 68, 23, 99, 246, 7, 70, 203, 254, 200, 206, 26, 209, 163, 232, 54, 103, 6, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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