Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 262b615aa396f17d3def886e8bb956efd88704de9281a95e83b7b009989812e2

Tx prefix hash: 961e148a391d991b699b87f6b38a9d335732b2b27efa447bc00d053ddb704503
Tx public key: a7e17bfcbf99c49c61d444e66e87910a16361be072b319ff7341c58f70dc8b2f
Timestamp: 1737616416 Timestamp [UCT]: 2025-01-23 07:13:36 Age [y:d:h:m:s]: 00:050:17:24:54
Block: 1203406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36077 RingCT/type: yes/0
Extra: 01a7e17bfcbf99c49c61d444e66e87910a16361be072b319ff7341c58f70dc8b2f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dbce72f198f1022ac1a87f8bc78ae3ccd13aeaf9fed7447ce4bb27d3cf420df 0.600000000000 1690083 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": 1203416, "vin": [ { "gen": { "height": 1203406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dbce72f198f1022ac1a87f8bc78ae3ccd13aeaf9fed7447ce4bb27d3cf420df" } } ], "extra": [ 1, 167, 225, 123, 252, 191, 153, 196, 156, 97, 212, 68, 230, 110, 135, 145, 10, 22, 54, 27, 224, 114, 179, 25, 255, 115, 65, 197, 143, 112, 220, 139, 47, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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