Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af644ec388df1416106c4b01cb2c2e9304b6691269d34f3abb1527e7ed086a4f

Tx prefix hash: a99bce6f1bd3046a3d674592c1b97b6a4ed1fc749f60adb0bba06ca6961e189d
Tx public key: 336f12a07e44bdb8ab06d5e5f577b57016a0b90f5ea173576ced9416f0defeb1
Timestamp: 1753896816 Timestamp [UCT]: 2025-07-30 17:33:36 Age [y:d:h:m:s]: 00:083:02:03:05
Block: 1336787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58198 RingCT/type: yes/0
Extra: 01336f12a07e44bdb8ab06d5e5f577b57016a0b90f5ea173576ced9416f0defeb10211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a3942a6936e302f33c3bbb67c9cad9343ce1e1f94952c02f7c05696f30d3a76 0.600000000000 1824590 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": 1336797, "vin": [ { "gen": { "height": 1336787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a3942a6936e302f33c3bbb67c9cad9343ce1e1f94952c02f7c05696f30d3a76" } } ], "extra": [ 1, 51, 111, 18, 160, 126, 68, 189, 184, 171, 6, 213, 229, 245, 119, 181, 112, 22, 160, 185, 15, 94, 161, 115, 87, 108, 237, 148, 22, 240, 222, 254, 177, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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