Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a21fd37a2e7c31186f42e3f56a3a26cc6c314f8fd638e3dae27cc5d9dba6980f

Tx prefix hash: 091325fde0b51172b89525f822277928a10bbf8acce0080baa8d40e7e2783446
Tx public key: 56ecd0c2bbfcb87208e371869934ccb85f43f8c851428dae6adc8d7660c10a49
Timestamp: 1716398745 Timestamp [UCT]: 2024-05-22 17:25:45 Age [y:d:h:m:s]: 00:234:20:28:57
Block: 1027693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168089 RingCT/type: yes/0
Extra: 0156ecd0c2bbfcb87208e371869934ccb85f43f8c851428dae6adc8d7660c10a490211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d4e6f652b866d9ba27d1a14e78997e70f29013814262e50534d741c1c41ca7 0.600000000000 1495452 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": 1027703, "vin": [ { "gen": { "height": 1027693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d4e6f652b866d9ba27d1a14e78997e70f29013814262e50534d741c1c41ca7" } } ], "extra": [ 1, 86, 236, 208, 194, 187, 252, 184, 114, 8, 227, 113, 134, 153, 52, 204, 184, 95, 67, 248, 200, 81, 66, 141, 174, 106, 220, 141, 118, 96, 193, 10, 73, 2, 17, 0, 0, 0, 4, 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