Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83850217d0781c7d62639faad858ae2a42de515702c1fed63602e03891648971

Tx prefix hash: 75c968c1c398075ee767302111f0d1ee0d5c6e100259beaad693fb58e072c815
Tx public key: f39fb2a9ac16b74518f2a9e6a0152004768a625ef59f4de3c9f5346c86d569a0
Timestamp: 1751263312 Timestamp [UCT]: 2025-06-30 06:01:52 Age [y:d:h:m:s]: 00:140:17:01:16
Block: 1315651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98753 RingCT/type: yes/0
Extra: 01f39fb2a9ac16b74518f2a9e6a0152004768a625ef59f4de3c9f5346c86d569a0021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66aa8d973718c3dad9f750a4dafde2faefd5e2e276a2a62bb85d2b0aa7753ce8 0.600000000000 1803306 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": 1315661, "vin": [ { "gen": { "height": 1315651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66aa8d973718c3dad9f750a4dafde2faefd5e2e276a2a62bb85d2b0aa7753ce8" } } ], "extra": [ 1, 243, 159, 178, 169, 172, 22, 183, 69, 24, 242, 169, 230, 160, 21, 32, 4, 118, 138, 98, 94, 245, 159, 77, 227, 201, 245, 52, 108, 134, 213, 105, 160, 2, 17, 0, 0, 0, 9, 191, 81, 178, 162, 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