Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b76ff52d4326f909343aefef3edba13e3bb49f37173c137832a2d11f2cb0e0e

Tx prefix hash: 189803a651b967a3e9c8188b19eb7048d32a03fa52006bc115a9d5ca782da67c
Tx public key: 6c16dfd2c07ec5cefecd67348b41c2ae57e5ab0d9c013b50ce3255126930f5ab
Timestamp: 1705624842 Timestamp [UCT]: 2024-01-19 00:40:42 Age [y:d:h:m:s]: 01:295:21:23:45
Block: 938362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470295 RingCT/type: yes/0
Extra: 016c16dfd2c07ec5cefecd67348b41c2ae57e5ab0d9c013b50ce3255126930f5ab02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aa33ee9afeb915d4d134b1c6237725066572ca1f08b47ed558b59aeda558b7c 0.600000000000 1396432 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": 938372, "vin": [ { "gen": { "height": 938362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aa33ee9afeb915d4d134b1c6237725066572ca1f08b47ed558b59aeda558b7c" } } ], "extra": [ 1, 108, 22, 223, 210, 192, 126, 197, 206, 254, 205, 103, 52, 139, 65, 194, 174, 87, 229, 171, 13, 156, 1, 59, 80, 206, 50, 85, 18, 105, 48, 245, 171, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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