Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e24baaf8998d0abdb9a28f31b0e2905bdfad59a5d6ffc7f39492e0790fd54736

Tx prefix hash: 4be5d38345eda9c1a7b8f43633b09001db9c392d741f3922dcbbac66becc015d
Tx public key: 444fc96ac6f712b7c40c12171d0fbfd8657adfeed295f36f9a32611f8867644d
Timestamp: 1752584155 Timestamp [UCT]: 2025-07-15 12:55:55 Age [y:d:h:m:s]: 00:128:15:08:58
Block: 1326029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90663 RingCT/type: yes/0
Extra: 01444fc96ac6f712b7c40c12171d0fbfd8657adfeed295f36f9a32611f8867644d02110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1ca254d63a948d45378be5a8db243b09b40b6ceb037dfb936cf06c6d3d895d7 0.600000000000 1813778 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": 1326039, "vin": [ { "gen": { "height": 1326029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1ca254d63a948d45378be5a8db243b09b40b6ceb037dfb936cf06c6d3d895d7" } } ], "extra": [ 1, 68, 79, 201, 106, 198, 247, 18, 183, 196, 12, 18, 23, 29, 15, 191, 216, 101, 122, 223, 238, 210, 149, 243, 111, 154, 50, 97, 31, 136, 103, 100, 77, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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