Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2937048cee7397990f6a9159b4d033b10034aba2437c76fe59bdcb56d9237586

Tx prefix hash: 2843c0dbb13bc88c82d80566ccca08daa81dd9b82cc34f45045db647c2c21a45
Tx public key: e92cb4a1bd3c66937712099e4c3e1025e5997b3a9064a4afe12766864e98b75a
Timestamp: 1698559885 Timestamp [UCT]: 2023-10-29 06:11:25 Age [y:d:h:m:s]: 01:118:14:12:37
Block: 880021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345708 RingCT/type: yes/0
Extra: 01e92cb4a1bd3c66937712099e4c3e1025e5997b3a9064a4afe12766864e98b75a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.744946571000 dcy

stealth address amount amount idx
00: f17a015184992c4133779cbea283951f29e88bf9a9a6a0dc5cbb26e6faa0a3cd 0.744946571000 1335563 of 0

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": 880031, "vin": [ { "gen": { "height": 880021 } } ], "vout": [ { "amount": 744946571, "target": { "key": "f17a015184992c4133779cbea283951f29e88bf9a9a6a0dc5cbb26e6faa0a3cd" } } ], "extra": [ 1, 233, 44, 180, 161, 189, 60, 102, 147, 119, 18, 9, 158, 76, 62, 16, 37, 229, 153, 123, 58, 144, 100, 164, 175, 225, 39, 102, 134, 78, 152, 183, 90, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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