Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e59608a2fee99fbbcf751fc2b1a9568e727263e17db16cf3947104f7041ac9d

Tx prefix hash: e065af457ea1216d3a19e8a3dd036776f9cf9279979503661339f43773a3d27b
Tx public key: 3415bc6fdb6c8ba20df30f4df703e72d20c6d05518c984ebcb51b686a495b7fe
Timestamp: 1742503539 Timestamp [UCT]: 2025-03-20 20:45:39 Age [y:d:h:m:s]: 00:309:07:32:54
Block: 1243664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218693 RingCT/type: yes/0
Extra: 013415bc6fdb6c8ba20df30f4df703e72d20c6d05518c984ebcb51b686a495b7fe021100000001bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f317d40984bbb438354bb68d462352cbd5978a4dfbfa06b2210564cee5b64434 0.600000000000 1730649 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": 1243674, "vin": [ { "gen": { "height": 1243664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f317d40984bbb438354bb68d462352cbd5978a4dfbfa06b2210564cee5b64434" } } ], "extra": [ 1, 52, 21, 188, 111, 219, 108, 139, 162, 13, 243, 15, 77, 247, 3, 231, 45, 32, 198, 208, 85, 24, 201, 132, 235, 203, 81, 182, 134, 164, 149, 183, 254, 2, 17, 0, 0, 0, 1, 191, 167, 118, 35, 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