Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b150c4f2825ca0b2de96ae49e1f7b24a4b9026ae1858c04d7fb935facaa53d

Tx prefix hash: 6cd4e822170052d52523a04e64ebc71d9e863af6f9d3a1b330345788c9290dd8
Tx public key: 19a2a34bd240d0ed9cfe00fa9b18d9e5aa095cc30524643afbbe85a76e9fcd28
Timestamp: 1703512327 Timestamp [UCT]: 2023-12-25 13:52:07 Age [y:d:h:m:s]: 01:317:02:54:59
Block: 920868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485463 RingCT/type: yes/0
Extra: 0119a2a34bd240d0ed9cfe00fa9b18d9e5aa095cc30524643afbbe85a76e9fcd28021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83680945dcd41e9387e567a2063643f4440b5875652b7949cb1be51203856eae 0.600000000000 1378552 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": 920878, "vin": [ { "gen": { "height": 920868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83680945dcd41e9387e567a2063643f4440b5875652b7949cb1be51203856eae" } } ], "extra": [ 1, 25, 162, 163, 75, 210, 64, 208, 237, 156, 254, 0, 250, 155, 24, 217, 229, 170, 9, 92, 195, 5, 36, 100, 58, 251, 190, 133, 167, 110, 159, 205, 40, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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