Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da2ba4ad6c7f9d4fb899a2de6688e421210a3c8c712418bc5657ac874fed706b

Tx prefix hash: 5ebb6b22e9ab64f335187beba3d6fdf5fba62ee6fe62d8d7f3676ee3d86e1b5b
Tx public key: 9838849b444482f7ec5a59140ff412c5004f37b97b20123ff9873a2863a16348
Timestamp: 1702824883 Timestamp [UCT]: 2023-12-17 14:54:43 Age [y:d:h:m:s]: 01:034:01:54:25
Block: 915161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285677 RingCT/type: yes/0
Extra: 019838849b444482f7ec5a59140ff412c5004f37b97b20123ff9873a2863a16348021100000006faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a68e3e964fe5cc166fa9ef65d4ac8b42a1f0ac0351e1c2adcde0740b1b122c7 0.600000000000 1372547 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": 915171, "vin": [ { "gen": { "height": 915161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a68e3e964fe5cc166fa9ef65d4ac8b42a1f0ac0351e1c2adcde0740b1b122c7" } } ], "extra": [ 1, 152, 56, 132, 155, 68, 68, 130, 247, 236, 90, 89, 20, 15, 244, 18, 197, 0, 79, 55, 185, 123, 32, 18, 63, 249, 135, 58, 40, 99, 161, 99, 72, 2, 17, 0, 0, 0, 6, 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