Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b04c646648cde2ebb2fc2584c97db832e12d8ca6424c0350c459881dd49631e

Tx prefix hash: 0b3788b55793df66f67f8dfcd6fecea4ba355ff4e99b2be052070dc419417dea
Tx public key: f770ad6cd957ef14648f1f89ad1f18b6fe9e17f81d34c0dd5b248e8a25d4d597
Timestamp: 1725824137 Timestamp [UCT]: 2024-09-08 19:35:37 Age [y:d:h:m:s]: 00:203:07:07:26
Block: 1105846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145118 RingCT/type: yes/0
Extra: 01f770ad6cd957ef14648f1f89ad1f18b6fe9e17f81d34c0dd5b248e8a25d4d597021100000007e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 53aa56a1afc3bd151f79d63ef4fd77c61b2fd22cd5557e4760ab4664d0167f4c 0.608000000000 1583323 of 0

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": 1105856, "vin": [ { "gen": { "height": 1105846 } } ], "vout": [ { "amount": 608000000, "target": { "key": "53aa56a1afc3bd151f79d63ef4fd77c61b2fd22cd5557e4760ab4664d0167f4c" } } ], "extra": [ 1, 247, 112, 173, 108, 217, 87, 239, 20, 100, 143, 31, 137, 173, 31, 24, 182, 254, 158, 23, 248, 29, 52, 192, 221, 91, 36, 142, 138, 37, 212, 213, 151, 2, 17, 0, 0, 0, 7, 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