Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07dd9f5dd7fe745790b79f8464f4db0770fa5eb444d91caa7c06a96c076cd05f

Tx prefix hash: a9d140d27b7f06e632ac05cf1a8a9e189085a9c2c13ee796b152ccb04aa6e2bc
Tx public key: 6d501e93b9a0e3cd4a470b75a3b2342212c1bc088b6ab3bd139b47f9c4e419d3
Timestamp: 1750456512 Timestamp [UCT]: 2025-06-20 21:55:12 Age [y:d:h:m:s]: 00:147:17:24:58
Block: 1309314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103426 RingCT/type: yes/0
Extra: 016d501e93b9a0e3cd4a470b75a3b2342212c1bc088b6ab3bd139b47f9c4e419d3021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8219646356626bf1a04fff9297f187b92c7c8583e34182b9b52a3e7523339b13 0.600000000000 1796929 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": 1309324, "vin": [ { "gen": { "height": 1309314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8219646356626bf1a04fff9297f187b92c7c8583e34182b9b52a3e7523339b13" } } ], "extra": [ 1, 109, 80, 30, 147, 185, 160, 227, 205, 74, 71, 11, 117, 163, 178, 52, 34, 18, 193, 188, 8, 139, 106, 179, 189, 19, 155, 71, 249, 196, 228, 25, 211, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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