Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5d84c0ecbe3e5a63939c24f2bde3b8c77512c00d8e06e70cfa0c7228fb8fd45

Tx prefix hash: 8d6769421cea6f4a570f509e80f951dd12cd57567c019845b913d49e1d1c22fd
Tx public key: 854f515d80089ace60fb4d4e9791baa7208f42ad6ff3e8975ec7318f7a501d8d
Timestamp: 1761154581 Timestamp [UCT]: 2025-10-22 17:36:21 Age [y:d:h:m:s]: 00:062:00:10:12
Block: 1395637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44382 RingCT/type: yes/0
Extra: 01854f515d80089ace60fb4d4e9791baa7208f42ad6ff3e8975ec7318f7a501d8d02110000000601491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6befd529cb440533641aefde295c3deb37eebe330b0db4dfcbfdb73af04143c 0.600000000000 1883920 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": 1395647, "vin": [ { "gen": { "height": 1395637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6befd529cb440533641aefde295c3deb37eebe330b0db4dfcbfdb73af04143c" } } ], "extra": [ 1, 133, 79, 81, 93, 128, 8, 154, 206, 96, 251, 77, 78, 151, 145, 186, 167, 32, 143, 66, 173, 111, 243, 232, 151, 94, 199, 49, 143, 122, 80, 29, 141, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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