Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c960f4e13409aaf585c98e8076def8364013be796f01359614bfbebfe41c13

Tx prefix hash: c6bb5c9a8381dc8cb5f7d42ee0bcd62f2b96a43d97738aa7dbc7d9c2e002f380
Tx public key: 0bea7a91ba3b881a1b2ef80cdc3ae45c27a0c3b72931b34b2e1c7c009dee95cf
Timestamp: 1729288927 Timestamp [UCT]: 2024-10-18 22:02:07 Age [y:d:h:m:s]: 00:222:18:35:26
Block: 1134565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159039 RingCT/type: yes/0
Extra: 010bea7a91ba3b881a1b2ef80cdc3ae45c27a0c3b72931b34b2e1c7c009dee95cf0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85e9246f18edd801dfd9441c8e744d68212aa34c405342d028427686a7ddf2a5 0.600000000000 1617886 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": 1134575, "vin": [ { "gen": { "height": 1134565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85e9246f18edd801dfd9441c8e744d68212aa34c405342d028427686a7ddf2a5" } } ], "extra": [ 1, 11, 234, 122, 145, 186, 59, 136, 26, 27, 46, 248, 12, 220, 58, 228, 92, 39, 160, 195, 183, 41, 49, 179, 75, 46, 28, 124, 0, 157, 238, 149, 207, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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