Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a0577de20916e0211b7f2f67b8b178b01e6c0aba208fbd1781489787756d44

Tx prefix hash: cc558d653682c3c4da631fabb3961c2f97e5a04491a49bc4400a0e942c47280d
Tx public key: d3ce99e102f961157f0b04f137e6a1c6225ab22bce5e107cc5c856e3c86ac6a9
Timestamp: 1702755652 Timestamp [UCT]: 2023-12-16 19:40:52 Age [y:d:h:m:s]: 01:035:08:29:20
Block: 914592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286582 RingCT/type: yes/0
Extra: 01d3ce99e102f961157f0b04f137e6a1c6225ab22bce5e107cc5c856e3c86ac6a902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83fad6442597d4b5bb3a79cc1c4eea2ad18108de93f9e7e4258809543488296e 0.600000000000 1371938 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": 914602, "vin": [ { "gen": { "height": 914592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83fad6442597d4b5bb3a79cc1c4eea2ad18108de93f9e7e4258809543488296e" } } ], "extra": [ 1, 211, 206, 153, 225, 2, 249, 97, 21, 127, 11, 4, 241, 55, 230, 161, 198, 34, 90, 178, 43, 206, 94, 16, 124, 197, 200, 86, 227, 200, 106, 198, 169, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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