Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcee61e3bfa0b8e75d1f7943b92277ed09080d1f17ded95a7f95cf9e6ef1324a

Tx prefix hash: bc27156523bdb5c807c5404d4b1447085fc9eb1a002e885b9741dddceba9e17e
Tx public key: 94e9f6aacdd2e8fa31a953f40073c150e405fe56923c6f0c7ad01047cd4f1ab4
Timestamp: 1582329907 Timestamp [UCT]: 2020-02-22 00:05:07 Age [y:d:h:m:s]: 05:021:06:00:59
Block: 69753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168460 RingCT/type: yes/0
Extra: 0194e9f6aacdd2e8fa31a953f40073c150e405fe56923c6f0c7ad01047cd4f1ab40211000000164ac5aa02000000000000000000

1 output(s) for total of 360.497847360000 dcy

stealth address amount amount idx
00: f65dd9fb670d3112cf3e5e6c36b2a8a72a4b7a5234f2a33506008d7d8b6c8e83 360.497847360000 128745 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": 69763, "vin": [ { "gen": { "height": 69753 } } ], "vout": [ { "amount": 360497847360, "target": { "key": "f65dd9fb670d3112cf3e5e6c36b2a8a72a4b7a5234f2a33506008d7d8b6c8e83" } } ], "extra": [ 1, 148, 233, 246, 170, 205, 210, 232, 250, 49, 169, 83, 244, 0, 115, 193, 80, 228, 5, 254, 86, 146, 60, 111, 12, 122, 208, 16, 71, 205, 79, 26, 180, 2, 17, 0, 0, 0, 22, 74, 197, 170, 2, 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