Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3e2cceb3886201f9fd5a7d8cdd91628b17328a686885cf0fad63428fb5f2e68

Tx prefix hash: 6508360f867ef80d2b75f2bad7a5c28ba6cea67cfd68e68e3aa87ea39df64b5b
Tx public key: d91833efac39fd3fe5a8c0fb0f45e2341e23ad13b55599510f0326cdcc13f449
Timestamp: 1636782815 Timestamp [UCT]: 2021-11-13 05:53:35 Age [y:d:h:m:s]: 03:122:09:59:57
Block: 373318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 865912 RingCT/type: yes/0
Extra: 01d91833efac39fd3fe5a8c0fb0f45e2341e23ad13b55599510f0326cdcc13f449021100000008a272b9cb000000000000000000

1 output(s) for total of 35.569053658000 dcy

stealth address amount amount idx
00: 59f5b1436a97d4f4ed0a207cec832d0342c8b5ecf1b6423e0f062954c1a0b712 35.569053658000 755970 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": 373328, "vin": [ { "gen": { "height": 373318 } } ], "vout": [ { "amount": 35569053658, "target": { "key": "59f5b1436a97d4f4ed0a207cec832d0342c8b5ecf1b6423e0f062954c1a0b712" } } ], "extra": [ 1, 217, 24, 51, 239, 172, 57, 253, 63, 229, 168, 192, 251, 15, 69, 226, 52, 30, 35, 173, 19, 181, 85, 153, 81, 15, 3, 38, 205, 204, 19, 244, 73, 2, 17, 0, 0, 0, 8, 162, 114, 185, 203, 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