Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e5222a1e2462688252dd9d833a9b30b6982ff7d521156aeca407460a3115a9

Tx prefix hash: 71baa631838d2e81e7f5628b0e1e58240a72e20a6481f0e73f02e3282da90bda
Tx public key: 735bef52d631ed4f2d21c765e3b5279626d449ae54da1d86cc82fc40680813b3
Timestamp: 1709495346 Timestamp [UCT]: 2024-03-03 19:49:06 Age [y:d:h:m:s]: 01:035:14:09:49
Block: 970471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286428 RingCT/type: yes/0
Extra: 01735bef52d631ed4f2d21c765e3b5279626d449ae54da1d86cc82fc40680813b302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da79e98c1e2228c79fae9d629b87fc7a11e306e40a78385dbed300e28bb3c923 0.600000000000 1430324 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": 970481, "vin": [ { "gen": { "height": 970471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da79e98c1e2228c79fae9d629b87fc7a11e306e40a78385dbed300e28bb3c923" } } ], "extra": [ 1, 115, 91, 239, 82, 214, 49, 237, 79, 45, 33, 199, 101, 227, 181, 39, 150, 38, 212, 73, 174, 84, 218, 29, 134, 204, 130, 252, 64, 104, 8, 19, 179, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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