Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5f84cb2e6e8c628d8d480ca47d8d7ff31d1e910a330af8f81aeedf9772140f9

Tx prefix hash: 8ee2501f52d703388ed600af329825ed6179749a2e560e5a7566cfa73e3c95f0
Tx public key: 9fac497c7d5f3f14eef79cff0d62c663cc2777db732acd5de4df3fa32df75b2c
Timestamp: 1697418981 Timestamp [UCT]: 2023-10-16 01:16:21 Age [y:d:h:m:s]: 01:211:08:05:37
Block: 870550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412101 RingCT/type: yes/0
Extra: 019fac497c7d5f3f14eef79cff0d62c663cc2777db732acd5de4df3fa32df75b2c02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.800767602000 dcy

stealth address amount amount idx
00: 2898636410243540c075f65e829d7b48afa09428fd2ca0c88cb9c92ff5ef16c9 0.800767602000 1325433 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": 870560, "vin": [ { "gen": { "height": 870550 } } ], "vout": [ { "amount": 800767602, "target": { "key": "2898636410243540c075f65e829d7b48afa09428fd2ca0c88cb9c92ff5ef16c9" } } ], "extra": [ 1, 159, 172, 73, 124, 125, 95, 63, 20, 238, 247, 156, 255, 13, 98, 198, 99, 204, 39, 119, 219, 115, 42, 205, 93, 228, 223, 63, 163, 45, 247, 91, 44, 2, 17, 0, 0, 0, 13, 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