Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7a0e0f1407fd9bc107f2c609f41bd37aad5bba648bb6063b420d657753210cd

Tx prefix hash: 883f6a5a4548c1bca699cb950b6c56ca2bb337a6848046b43aa1e4fb901d2fd2
Tx public key: abcee7ecc78d4a67ee991005e0e0308d60e3ce50632b01dc8b18698dc7208e01
Timestamp: 1705109161 Timestamp [UCT]: 2024-01-13 01:26:01 Age [y:d:h:m:s]: 01:114:18:17:18
Block: 934082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343153 RingCT/type: yes/0
Extra: 01abcee7ecc78d4a67ee991005e0e0308d60e3ce50632b01dc8b18698dc7208e0102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d07cd5c4534b7a4e0314111d7cbb3d360287339b162023e32ec1b584ca6bb906 0.600000000000 1392068 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": 934092, "vin": [ { "gen": { "height": 934082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d07cd5c4534b7a4e0314111d7cbb3d360287339b162023e32ec1b584ca6bb906" } } ], "extra": [ 1, 171, 206, 231, 236, 199, 141, 74, 103, 238, 153, 16, 5, 224, 224, 48, 141, 96, 227, 206, 80, 99, 43, 1, 220, 139, 24, 105, 141, 199, 32, 142, 1, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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