Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17d5765e8e6042555416244b1d703cea5d2391b29e32672768410f37b76600fd

Tx prefix hash: 7fdda411f9f0e4ceaf97b42939a8b4603e77a52a20af05cd2f431ae98350b7c2
Tx public key: 2a260ca2d73d205ccd15a5afed21e685ae0e441815a12946b1788b631b5ee336
Timestamp: 1724725727 Timestamp [UCT]: 2024-08-27 02:28:47 Age [y:d:h:m:s]: 01:069:13:32:19
Block: 1096721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308167 RingCT/type: yes/0
Extra: 012a260ca2d73d205ccd15a5afed21e685ae0e441815a12946b1788b631b5ee336021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af5a0765aaace5bda8dcb19e87fd721db8192213dc5b32c7ee982e140de6936b 0.600000000000 1571916 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": 1096731, "vin": [ { "gen": { "height": 1096721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af5a0765aaace5bda8dcb19e87fd721db8192213dc5b32c7ee982e140de6936b" } } ], "extra": [ 1, 42, 38, 12, 162, 215, 61, 32, 92, 205, 21, 165, 175, 237, 33, 230, 133, 174, 14, 68, 24, 21, 161, 41, 70, 177, 120, 139, 99, 27, 94, 227, 54, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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