Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0286b8ee33818cbccbd46e97bff10e150cc7ef1fce97ab7a53bfdd8c9d76f46

Tx prefix hash: 6b0588721cfa8745c40f0a8319f0c9f0583157c6a9af757333820301bb0f24ec
Tx public key: b5008e70fe70b508267ab367450f6b8bb715e66b6a644a56647c1b0fb88e2647
Timestamp: 1720038925 Timestamp [UCT]: 2024-07-03 20:35:25 Age [y:d:h:m:s]: 00:280:08:56:27
Block: 1057870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200339 RingCT/type: yes/0
Extra: 01b5008e70fe70b508267ab367450f6b8bb715e66b6a644a56647c1b0fb88e26470211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e44ed5c1fb0af1ccdadb1e0b4c48800a1afc1f27dfb9c6a34db285f29fe41470 0.600000000000 1528313 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": 1057880, "vin": [ { "gen": { "height": 1057870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e44ed5c1fb0af1ccdadb1e0b4c48800a1afc1f27dfb9c6a34db285f29fe41470" } } ], "extra": [ 1, 181, 0, 142, 112, 254, 112, 181, 8, 38, 122, 179, 103, 69, 15, 107, 139, 183, 21, 230, 107, 106, 100, 74, 86, 100, 124, 27, 15, 184, 142, 38, 71, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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