Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2badc1ec1bee7eaddd6f8c27947fd07e78fe73e6ddf8faf523cb92da33ef3206

Tx prefix hash: 73d440d30ea5e14c7dd5eb269d29b2a8cee75ce0b70071c3339858018e10ef56
Tx public key: b6631ed1cf72e8d0b26ee04afef3dcaae0d76695e2bdaf2240608012ef1b7a37
Timestamp: 1711326329 Timestamp [UCT]: 2024-03-25 00:25:29 Age [y:d:h:m:s]: 01:084:17:57:56
Block: 985668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321446 RingCT/type: yes/0
Extra: 01b6631ed1cf72e8d0b26ee04afef3dcaae0d76695e2bdaf2240608012ef1b7a370211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87ca83692f8abd05c665f6a8801cdb00a5455f419d76996e3dce5c15d5598330 0.600000000000 1445885 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": 985678, "vin": [ { "gen": { "height": 985668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87ca83692f8abd05c665f6a8801cdb00a5455f419d76996e3dce5c15d5598330" } } ], "extra": [ 1, 182, 99, 30, 209, 207, 114, 232, 208, 178, 110, 224, 74, 254, 243, 220, 170, 224, 215, 102, 149, 226, 189, 175, 34, 64, 96, 128, 18, 239, 27, 122, 55, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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