Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1346478b517179fb501b79ff169a3412b04c818946f46eb4b057e4077977cc65

Tx prefix hash: 4bbc8a5ff1cdc1ecd5692424bb687d0f7bf18a55b2176100ce6fdf9155253465
Tx public key: 8f3a901c79accbbd1c12b7fc2cc773acdea703a2db1569fbf498e6ed4c5d7c99
Timestamp: 1747784127 Timestamp [UCT]: 2025-05-20 23:35:27 Age [y:d:h:m:s]: 00:181:09:42:12
Block: 1287371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127343 RingCT/type: yes/0
Extra: 018f3a901c79accbbd1c12b7fc2cc773acdea703a2db1569fbf498e6ed4c5d7c9902110000000a1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68b70c465139d650415a0c5e3a262b61df90985bceaf869138da37d19fedd94 0.600000000000 1774838 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": 1287381, "vin": [ { "gen": { "height": 1287371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68b70c465139d650415a0c5e3a262b61df90985bceaf869138da37d19fedd94" } } ], "extra": [ 1, 143, 58, 144, 28, 121, 172, 203, 189, 28, 18, 183, 252, 44, 199, 115, 172, 222, 167, 3, 162, 219, 21, 105, 251, 244, 152, 230, 237, 76, 93, 124, 153, 2, 17, 0, 0, 0, 10, 31, 144, 81, 122, 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