Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7911d807d02aabe9ac858f27e64bf43af4bee4be13f0ec5bba878303f85c5bf2

Tx prefix hash: d8354983b39a5b950814741f8e620e2b8d543314d983d29aac6f733fc5f287a7
Tx public key: 34c1f62ba76b4553ada118bcd32b60f4b47ae8bfa34ae99196e1d1ca7dc6ce20
Timestamp: 1736597992 Timestamp [UCT]: 2025-01-11 12:19:52 Age [y:d:h:m:s]: 00:070:14:50:30
Block: 1195013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50256 RingCT/type: yes/0
Extra: 0134c1f62ba76b4553ada118bcd32b60f4b47ae8bfa34ae99196e1d1ca7dc6ce200211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82039842c1525c14ec91d124085637437e80d307e1db18ce0a0f3781782f4372 0.600000000000 1681598 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": 1195023, "vin": [ { "gen": { "height": 1195013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82039842c1525c14ec91d124085637437e80d307e1db18ce0a0f3781782f4372" } } ], "extra": [ 1, 52, 193, 246, 43, 167, 107, 69, 83, 173, 161, 24, 188, 211, 43, 96, 244, 180, 122, 232, 191, 163, 74, 233, 145, 150, 225, 209, 202, 125, 198, 206, 32, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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