Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 458547832250e458e14c62dfdd9af0a64c9c20ce4d97d527bdcfcee711d0b79d

Tx prefix hash: acf7605ae64298c42f450d7abef08b527c17ed75a0d51a0abe93125f50d40359
Tx public key: 24e625e6b849e7b625877f3ba3b29cbbd2dad84426982d54d50a5378cab83449
Timestamp: 1700435275 Timestamp [UCT]: 2023-11-19 23:07:55 Age [y:d:h:m:s]: 02:000:04:00:13
Block: 895350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519896 RingCT/type: yes/0
Extra: 0124e625e6b849e7b625877f3ba3b29cbbd2dad84426982d54d50a5378cab83449021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.662725624000 dcy

stealth address amount amount idx
00: b98acb32b83ff4eb2981285950d2d04802d2577f3e7c5331e9558965cbd082b2 0.662725624000 1351581 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": 895360, "vin": [ { "gen": { "height": 895350 } } ], "vout": [ { "amount": 662725624, "target": { "key": "b98acb32b83ff4eb2981285950d2d04802d2577f3e7c5331e9558965cbd082b2" } } ], "extra": [ 1, 36, 230, 37, 230, 184, 73, 231, 182, 37, 135, 127, 59, 163, 178, 156, 187, 210, 218, 216, 68, 38, 152, 45, 84, 213, 10, 83, 120, 202, 184, 52, 73, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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