Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32f620eeb5c0e5a8b108b0bdde6ea2b693d4429ce365b076f9d9c305fc425e0a

Tx prefix hash: 1f2b440eb3fe34787b9eda2cc00fc9fdbd661041d82558a32a4acd9977062fed
Tx public key: 0d7adf42b3358b1f3d154ed99e5a4824ebdde4f2f77bfe9146e804db9b56d74e
Timestamp: 1696556865 Timestamp [UCT]: 2023-10-06 01:47:45 Age [y:d:h:m:s]: 01:098:17:07:29
Block: 863399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331814 RingCT/type: yes/0
Extra: 010d7adf42b3358b1f3d154ed99e5a4824ebdde4f2f77bfe9146e804db9b56d74e021100000009faf35c9c000000000000000000

1 output(s) for total of 0.845669633000 dcy

stealth address amount amount idx
00: 8488fab0a6c8078fc31af57996113d3b7f2d3bab25d7fe2af1e34fd012447e69 0.845669633000 1317851 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": 863409, "vin": [ { "gen": { "height": 863399 } } ], "vout": [ { "amount": 845669633, "target": { "key": "8488fab0a6c8078fc31af57996113d3b7f2d3bab25d7fe2af1e34fd012447e69" } } ], "extra": [ 1, 13, 122, 223, 66, 179, 53, 139, 31, 61, 21, 78, 217, 158, 90, 72, 36, 235, 221, 228, 242, 247, 123, 254, 145, 70, 232, 4, 219, 155, 86, 215, 78, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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