Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb9dca1d248379f6e98cec7855e8ee235404a95eea5b515aac65957b10bf7bdb

Tx prefix hash: 8965d8ead2d4b32abb0d86ee531ff84f24ac100275cef32a5049988f875db8e1
Tx public key: 78466d9fba3f0dc516036b8ab2d285456a5525093db18d7124de3b04d568a211
Timestamp: 1696085050 Timestamp [UCT]: 2023-09-30 14:44:10 Age [y:d:h:m:s]: 01:104:17:18:00
Block: 859488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336118 RingCT/type: yes/0
Extra: 0178466d9fba3f0dc516036b8ab2d285456a5525093db18d7124de3b04d568a2110211000000084b8f5122000000000000000000

1 output(s) for total of 0.871283537000 dcy

stealth address amount amount idx
00: 50a9e053dd21c87618b450582b12d46fcc8635070a88fb4bb97527f1781a26c4 0.871283537000 1313716 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": 859498, "vin": [ { "gen": { "height": 859488 } } ], "vout": [ { "amount": 871283537, "target": { "key": "50a9e053dd21c87618b450582b12d46fcc8635070a88fb4bb97527f1781a26c4" } } ], "extra": [ 1, 120, 70, 109, 159, 186, 63, 13, 197, 22, 3, 107, 138, 178, 210, 133, 69, 106, 85, 37, 9, 61, 177, 141, 113, 36, 222, 59, 4, 213, 104, 162, 17, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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