Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c1a2c9d21bc04c95727d711d0b1e1b97bb66807dd66dff179f07b1f2805650c

Tx prefix hash: e8bf806c7c24429eb7f87b7136023bcf6630f44329af0b9d89f96b4c94f07ca7
Tx public key: 22ddb8fead5ae8b11aa6eac37ad6e40080d7fc520158bf987df05671b194ea3e
Timestamp: 1762466437 Timestamp [UCT]: 2025-11-06 22:00:37 Age [y:d:h:m:s]: 00:061:14:12:21
Block: 1406497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44110 RingCT/type: yes/0
Extra: 0122ddb8fead5ae8b11aa6eac37ad6e40080d7fc520158bf987df05671b194ea3e02110000000adf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0315440b2f0cc2024b0e42106c80870d4109caf7fb9682337d7446945c3060f 0.600000000000 1894884 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": 1406507, "vin": [ { "gen": { "height": 1406497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0315440b2f0cc2024b0e42106c80870d4109caf7fb9682337d7446945c3060f" } } ], "extra": [ 1, 34, 221, 184, 254, 173, 90, 232, 177, 26, 166, 234, 195, 122, 214, 228, 0, 128, 215, 252, 82, 1, 88, 191, 152, 125, 240, 86, 113, 177, 148, 234, 62, 2, 17, 0, 0, 0, 10, 223, 90, 36, 122, 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