Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b8a4e7714c005191ae1945867596d54240b47a042dc3ea77708096c73e46a3

Tx prefix hash: e5d065b621cab9493cc4611e0ad49e27dba627acfb8ff6ed5a1eeba0eed1cb82
Tx public key: 145ae8dbe224ef1f952dc0363f1a4e05f0c5cad754faef73e89bc9977e418690
Timestamp: 1745773177 Timestamp [UCT]: 2025-04-27 16:59:37 Age [y:d:h:m:s]: 00:040:15:21:43
Block: 1270714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29075 RingCT/type: yes/0
Extra: 01145ae8dbe224ef1f952dc0363f1a4e05f0c5cad754faef73e89bc9977e41869002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a4f13b639820e429dc780fb5ea074cc3935a6a2429c5c28d8b3087dc46c453 0.600000000000 1757959 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": 1270724, "vin": [ { "gen": { "height": 1270714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a4f13b639820e429dc780fb5ea074cc3935a6a2429c5c28d8b3087dc46c453" } } ], "extra": [ 1, 20, 90, 232, 219, 226, 36, 239, 31, 149, 45, 192, 54, 63, 26, 78, 5, 240, 197, 202, 215, 84, 250, 239, 115, 232, 155, 201, 151, 126, 65, 134, 144, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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