Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4394817cd8a117462a7c2b5a255eabe7a27e839242f5d743a69fda963c13857c

Tx prefix hash: 5b3673eb5ec0dbc0bfddb2140874832f8e332d766183efae791683095d1505f8
Tx public key: 18645af5055c9c8302a265213cf3c62176f5dfe3f6acf56e6ce8fe73b6520498
Timestamp: 1700439654 Timestamp [UCT]: 2023-11-20 00:20:54 Age [y:d:h:m:s]: 01:101:05:53:15
Block: 895392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333508 RingCT/type: yes/0
Extra: 0118645af5055c9c8302a265213cf3c62176f5dfe3f6acf56e6ce8fe73b65204980211000000034b8f5122000000000000000000

1 output(s) for total of 0.662513297000 dcy

stealth address amount amount idx
00: c108a2731e2902bf945945a0b4d1b38042135b407ae11d125dcc9ab4bb18a6f0 0.662513297000 1351625 of 0

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": 895402, "vin": [ { "gen": { "height": 895392 } } ], "vout": [ { "amount": 662513297, "target": { "key": "c108a2731e2902bf945945a0b4d1b38042135b407ae11d125dcc9ab4bb18a6f0" } } ], "extra": [ 1, 24, 100, 90, 245, 5, 92, 156, 131, 2, 162, 101, 33, 60, 243, 198, 33, 118, 245, 223, 227, 246, 172, 245, 110, 108, 232, 254, 115, 182, 82, 4, 152, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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