Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f78dbdbfc46d886b8d3cf2813b5bc2dfcd0731c69c5977a213aa7634a7da2619

Tx prefix hash: 29afcb7810f06219e7f49952d1ae02032d60492b97de8bbd3c0fdd0ea6ac5ee7
Tx public key: 84217cc81e5e428cb861619323ca4146b2867b01b25a343900d449403694f1ca
Timestamp: 1748992403 Timestamp [UCT]: 2025-06-03 23:13:23 Age [y:d:h:m:s]: 00:170:04:07:05
Block: 1297374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119291 RingCT/type: yes/0
Extra: 0184217cc81e5e428cb861619323ca4146b2867b01b25a343900d449403694f1ca02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4f4d17d61ef5254b9e84f3d0e15ccd81c6aa4a719be482a835ba6adc5ae95a7 0.600000000000 1784891 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": 1297384, "vin": [ { "gen": { "height": 1297374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4f4d17d61ef5254b9e84f3d0e15ccd81c6aa4a719be482a835ba6adc5ae95a7" } } ], "extra": [ 1, 132, 33, 124, 200, 30, 94, 66, 140, 184, 97, 97, 147, 35, 202, 65, 70, 178, 134, 123, 1, 178, 90, 52, 57, 0, 212, 73, 64, 54, 148, 241, 202, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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