Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1efc29c4e413db93557a0db2c8b81c9f12dccc77b53cf4d7462af4b3d1ffe7d7

Tx prefix hash: bc1a452ce1b8081c5c1fe308e68cb2318cf4573108c463a9183aa59adcfc1b6d
Tx public key: 32a350c09621deabdcd7c84c493b349720380e98e55c613387d0e19750f81168
Timestamp: 1695514413 Timestamp [UCT]: 2023-09-24 00:13:33 Age [y:d:h:m:s]: 01:200:00:56:38
Block: 854759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404035 RingCT/type: yes/0
Extra: 0132a350c09621deabdcd7c84c493b349720380e98e55c613387d0e19750f81168021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.903293022000 dcy

stealth address amount amount idx
00: ee8c6a695b7069fd22118474d4755fa014f54747cd276655ded08745145f843c 0.903293022000 1308747 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": 854769, "vin": [ { "gen": { "height": 854759 } } ], "vout": [ { "amount": 903293022, "target": { "key": "ee8c6a695b7069fd22118474d4755fa014f54747cd276655ded08745145f843c" } } ], "extra": [ 1, 50, 163, 80, 192, 150, 33, 222, 171, 220, 215, 200, 76, 73, 59, 52, 151, 32, 56, 14, 152, 229, 92, 97, 51, 135, 208, 225, 151, 80, 248, 17, 104, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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