Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63fc05d61068dad9b7666774c000324592e0022a6d775a77d4a7c38726326994

Tx prefix hash: 6ca9f81359dc0ff5b68efb4775ffa8866feb278c3a9eed3d7078f781f55e50cc
Tx public key: e942a0e2bdb1c4666e79c75e32f4e217e44c8447c7f75c26aa14739d2ee8533a
Timestamp: 1637960120 Timestamp [UCT]: 2021-11-26 20:55:20 Age [y:d:h:m:s]: 03:072:09:00:57
Block: 382793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 830366 RingCT/type: yes/0
Extra: 01e942a0e2bdb1c4666e79c75e32f4e217e44c8447c7f75c26aa14739d2ee8533a02110000003bb494d89c000000000000000000

1 output(s) for total of 33.086304528000 dcy

stealth address amount amount idx
00: 3e38a65cb09fcfb6ae731e64885a9c4fe0cfe9fd29e6ea013f36b9fc0520b900 33.086304528000 772980 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": 382803, "vin": [ { "gen": { "height": 382793 } } ], "vout": [ { "amount": 33086304528, "target": { "key": "3e38a65cb09fcfb6ae731e64885a9c4fe0cfe9fd29e6ea013f36b9fc0520b900" } } ], "extra": [ 1, 233, 66, 160, 226, 189, 177, 196, 102, 110, 121, 199, 94, 50, 244, 226, 23, 228, 76, 132, 71, 199, 247, 92, 38, 170, 20, 115, 157, 46, 232, 83, 58, 2, 17, 0, 0, 0, 59, 180, 148, 216, 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