Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bde6952fe4169777d95fe06758c9cfe83e875ec81d086960695103da2952e4a8

Tx prefix hash: c877c4cfb9ae22c04b825eb21f1d66d7c4988db483e188a91ecb6d61e72b4398
Tx public key: e8c17080e94c10df581c433c907d7604b3192f0a8afed1705834b13e0b7810b3
Timestamp: 1714414764 Timestamp [UCT]: 2024-04-29 18:19:24 Age [y:d:h:m:s]: 00:294:04:48:01
Block: 1011243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210267 RingCT/type: yes/0
Extra: 01e8c17080e94c10df581c433c907d7604b3192f0a8afed1705834b13e0b7810b30211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a55d6151855098c7dae280b2b39327d97f6b6b32fc2e43bd9a93fe6d356acd6d 0.600000000000 1473421 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": 1011253, "vin": [ { "gen": { "height": 1011243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a55d6151855098c7dae280b2b39327d97f6b6b32fc2e43bd9a93fe6d356acd6d" } } ], "extra": [ 1, 232, 193, 112, 128, 233, 76, 16, 223, 88, 28, 67, 60, 144, 125, 118, 4, 179, 25, 47, 10, 138, 254, 209, 112, 88, 52, 177, 62, 11, 120, 16, 179, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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