Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ba6d0f8c1c5e6c04f6595b0fec192cda7a3455a999196d6953b3942f0509172

Tx prefix hash: 3d6cb9c79372e579d3216098937c86c8c49416d3c011a65e9a64448658e2a8c5
Tx public key: b3f2e9486a918a54ca24d568b727011bb49534ba0cdcbfe6dc2a5f6cb9e768de
Timestamp: 1730892003 Timestamp [UCT]: 2024-11-06 11:20:03 Age [y:d:h:m:s]: 00:109:11:43:54
Block: 1147764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78053 RingCT/type: yes/0
Extra: 01b3f2e9486a918a54ca24d568b727011bb49534ba0cdcbfe6dc2a5f6cb9e768de021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a054ab8615bd4c166e1d2dc28ed17e48bd25266b3f510c1bd8bc6a860e42ebc3 0.600000000000 1632465 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": 1147774, "vin": [ { "gen": { "height": 1147764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a054ab8615bd4c166e1d2dc28ed17e48bd25266b3f510c1bd8bc6a860e42ebc3" } } ], "extra": [ 1, 179, 242, 233, 72, 106, 145, 138, 84, 202, 36, 213, 104, 183, 39, 1, 27, 180, 149, 52, 186, 12, 220, 191, 230, 220, 42, 95, 108, 185, 231, 104, 222, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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