Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0be92f3b8da0b9b239b6ea4b24f14ce859f8bc4a4aad72ecf22d52b87f2da3ad

Tx prefix hash: c2bf9b5a91b8a93946cf47652e61ce1fcfd3fdf11ffc3a8f68e0c1ac9c73c1ed
Tx public key: 640775a0d34cfad3c0383f000bc9cabb2413e2936d68e1fd406d95d31cb16893
Timestamp: 1724196995 Timestamp [UCT]: 2024-08-20 23:36:35 Age [y:d:h:m:s]: 00:095:15:46:29
Block: 1092354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68426 RingCT/type: yes/0
Extra: 01640775a0d34cfad3c0383f000bc9cabb2413e2936d68e1fd406d95d31cb16893021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3513cdead9d51c4966955391c46e78a21144f966be9c3eaefe8073c990426ebb 0.600000000000 1567081 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": 1092364, "vin": [ { "gen": { "height": 1092354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3513cdead9d51c4966955391c46e78a21144f966be9c3eaefe8073c990426ebb" } } ], "extra": [ 1, 100, 7, 117, 160, 211, 76, 250, 211, 192, 56, 63, 0, 11, 201, 202, 187, 36, 19, 226, 147, 109, 104, 225, 253, 64, 109, 149, 211, 28, 177, 104, 147, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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