Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b297e3808db04cff1ce97364d22728b9b960d972a6d540acd457795c0ada91d

Tx prefix hash: 3f1712cc67ea42a8d705519298a76a747a0b0a3cdcd403f33f00fa3c7129cbfa
Tx public key: acb2643d0b0e99b770e5b2bf0b7fdcb14be1fe952104446da7c88ec146f2c205
Timestamp: 1750587288 Timestamp [UCT]: 2025-06-22 10:14:48 Age [y:d:h:m:s]: 00:150:16:01:38
Block: 1310389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105549 RingCT/type: yes/0
Extra: 01acb2643d0b0e99b770e5b2bf0b7fdcb14be1fe952104446da7c88ec146f2c205021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19f1014079bafdac4a9080ce5c344149d1358cb38cae7efe592e8b26d24340b8 0.600000000000 1798008 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": 1310399, "vin": [ { "gen": { "height": 1310389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19f1014079bafdac4a9080ce5c344149d1358cb38cae7efe592e8b26d24340b8" } } ], "extra": [ 1, 172, 178, 100, 61, 11, 14, 153, 183, 112, 229, 178, 191, 11, 127, 220, 177, 75, 225, 254, 149, 33, 4, 68, 109, 167, 200, 142, 193, 70, 242, 194, 5, 2, 17, 0, 0, 0, 1, 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