Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 008064f6c02250305a25bfdcc8fcd41083f0634f0418dd0fbf9450b2ee266511

Tx prefix hash: 2b7a3d27bd2c1e74564abfee4e34c31bf6f4e9f07479bfb4e86f14c5079d49a7
Tx public key: 21c458b0dfdf5f5dbc20b58b914ffa7d0afc97ebad5b5e6bfaff191b9faf6fa7
Timestamp: 1688879445 Timestamp [UCT]: 2023-07-09 05:10:45 Age [y:d:h:m:s]: 01:196:20:25:53
Block: 799805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402008 RingCT/type: yes/0
Extra: 0121c458b0dfdf5f5dbc20b58b914ffa7d0afc97ebad5b5e6bfaff191b9faf6fa7021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.373770386000 dcy

stealth address amount amount idx
00: 3327626da38054af79ca5d9ab05b0ae5394e91da480b6c810fbee95140f0c07c 1.373770386000 1250834 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": 799815, "vin": [ { "gen": { "height": 799805 } } ], "vout": [ { "amount": 1373770386, "target": { "key": "3327626da38054af79ca5d9ab05b0ae5394e91da480b6c810fbee95140f0c07c" } } ], "extra": [ 1, 33, 196, 88, 176, 223, 223, 95, 93, 188, 32, 181, 139, 145, 79, 250, 125, 10, 252, 151, 235, 173, 91, 94, 107, 250, 255, 25, 27, 159, 175, 111, 167, 2, 17, 0, 0, 0, 2, 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