Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc6794490f91c45e6a52b8fb29d3a02cd2be4aa84f5c7709b632196f79070a4

Tx prefix hash: 604ffa85d2cc04dd400489b68e2aae114c7036e46f59720aa2f27a8310957101
Tx public key: f7b946e8f2c125eda06b2f18a909f5e06589993b433091e779b78e48c88054a7
Timestamp: 1758897169 Timestamp [UCT]: 2025-09-26 14:32:49 Age [y:d:h:m:s]: 00:104:13:50:07
Block: 1376924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74875 RingCT/type: yes/0
Extra: 01f7b946e8f2c125eda06b2f18a909f5e06589993b433091e779b78e48c88054a702110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 219b34e6ca186074b3384c6e29324c5a0c4cd9e09ed77acc44f60446ecef912e 0.600000000000 1865015 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": 1376934, "vin": [ { "gen": { "height": 1376924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "219b34e6ca186074b3384c6e29324c5a0c4cd9e09ed77acc44f60446ecef912e" } } ], "extra": [ 1, 247, 185, 70, 232, 242, 193, 37, 237, 160, 107, 47, 24, 169, 9, 245, 224, 101, 137, 153, 59, 67, 48, 145, 231, 121, 183, 142, 72, 200, 128, 84, 167, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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