Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af1b64dae7503017d74f3a8ca2f316f44faf129b570bdac2f14b799c1000b34d

Tx prefix hash: c77d2b6a5eacfe6af3b6e4649281b8939289df762e9af3ec5218bcc7d8e846c8
Tx public key: df15fd98f55bc73f24a8743e851b7d1777c524836c884c82c978c972ef77b2e8
Timestamp: 1755452631 Timestamp [UCT]: 2025-08-17 17:43:51 Age [y:d:h:m:s]: 00:167:00:48:31
Block: 1348650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119141 RingCT/type: yes/0
Extra: 01df15fd98f55bc73f24a8743e851b7d1777c524836c884c82c978c972ef77b2e8021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f62ce65a8dc28d26c19919f716abdf5ca972a3bcf30ce8e5360d81f58012d3e 0.600000000000 1836577 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": 1348660, "vin": [ { "gen": { "height": 1348650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f62ce65a8dc28d26c19919f716abdf5ca972a3bcf30ce8e5360d81f58012d3e" } } ], "extra": [ 1, 223, 21, 253, 152, 245, 91, 199, 63, 36, 168, 116, 62, 133, 27, 125, 23, 119, 197, 36, 131, 108, 136, 76, 130, 201, 120, 201, 114, 239, 119, 178, 232, 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