Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b8b4c464b6392ac594c281092b2a4c6d87b66c7fe52c3169e0b61901922bf3

Tx prefix hash: 90d1c57ee570d3acc02e23078079f4abdbb86000fd0534f7d0a1be6f9af0836a
Tx public key: 464ba5ef63dd3aa723b75dc1476ff0df3ba8724db1a8c0c9b66ab8eb1cd7c438
Timestamp: 1699506566 Timestamp [UCT]: 2023-11-09 05:09:26 Age [y:d:h:m:s]: 01:150:10:08:24
Block: 887658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368692 RingCT/type: yes/0
Extra: 01464ba5ef63dd3aa723b75dc1476ff0df3ba8724db1a8c0c9b66ab8eb1cd7c43802110000000be6d27f9c000000000000000000

1 output(s) for total of 0.702781892000 dcy

stealth address amount amount idx
00: cba067d0dbac8848975bf8d953edf734fb1579e413a628ca6c2762cb480644be 0.702781892000 1343551 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": 887668, "vin": [ { "gen": { "height": 887658 } } ], "vout": [ { "amount": 702781892, "target": { "key": "cba067d0dbac8848975bf8d953edf734fb1579e413a628ca6c2762cb480644be" } } ], "extra": [ 1, 70, 75, 165, 239, 99, 221, 58, 167, 35, 183, 93, 193, 71, 111, 240, 223, 59, 168, 114, 77, 177, 168, 192, 201, 182, 106, 184, 235, 28, 215, 196, 56, 2, 17, 0, 0, 0, 11, 230, 210, 127, 156, 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