Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2c45c70b8ee3e9b6462639b43c75027594fc6025e74bb576b74da6f0c880b1

Tx prefix hash: 4d0bce5f31cef9c7dab48d9bdc2a987c9f394365b5ac1c896917032050f15732
Tx public key: 0cf28e4dbe57c8277a5c43820cf6b5e8ccf0fb423148a4bf591c0cd5495ad61d
Timestamp: 1607966828 Timestamp [UCT]: 2020-12-14 17:27:08 Age [y:d:h:m:s]: 04:052:02:29:35
Block: 162039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1049384 RingCT/type: yes/0
Extra: 010cf28e4dbe57c8277a5c43820cf6b5e8ccf0fb423148a4bf591c0cd5495ad61d0211000001f427e2517e000000000000000000

1 output(s) for total of 178.278185351000 dcy

stealth address amount amount idx
00: 20484bf72bfb1b1b8858d68dcd4c0ac07bb75facc09e95e3df7b8d0c236d7d51 178.278185351000 288490 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": 162049, "vin": [ { "gen": { "height": 162039 } } ], "vout": [ { "amount": 178278185351, "target": { "key": "20484bf72bfb1b1b8858d68dcd4c0ac07bb75facc09e95e3df7b8d0c236d7d51" } } ], "extra": [ 1, 12, 242, 142, 77, 190, 87, 200, 39, 122, 92, 67, 130, 12, 246, 181, 232, 204, 240, 251, 66, 49, 72, 164, 191, 89, 28, 12, 213, 73, 90, 214, 29, 2, 17, 0, 0, 1, 244, 39, 226, 81, 126, 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