Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76e62312eddb29aa9a395d7bb5c6a534e0538bf765b4dbef4f63ee99d8dc1b95

Tx prefix hash: 9feacc8be9d0f660f29f959c9b12c8486c1e52f6af4e294e39d737417352a024
Tx public key: ad909b5f454a0b9415d27bb5edf13a1ffcd4dbab56f9e20f551104a48dc73829
Timestamp: 1727315413 Timestamp [UCT]: 2024-09-26 01:50:13 Age [y:d:h:m:s]: 00:208:03:41:35
Block: 1118202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148586 RingCT/type: yes/0
Extra: 01ad909b5f454a0b9415d27bb5edf13a1ffcd4dbab56f9e20f551104a48dc73829021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eab5123ead9ad0237539f6f386f66318a21e8a1bf102543c72b8105b27039692 0.600000000000 1599313 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": 1118212, "vin": [ { "gen": { "height": 1118202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eab5123ead9ad0237539f6f386f66318a21e8a1bf102543c72b8105b27039692" } } ], "extra": [ 1, 173, 144, 155, 95, 69, 74, 11, 148, 21, 210, 123, 181, 237, 241, 58, 31, 252, 212, 219, 171, 86, 249, 226, 15, 85, 17, 4, 164, 141, 199, 56, 41, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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