Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96a6a0d0c82a175937c599eb16ae7d64ab2a3880715b601fd583526bba4b847c

Tx prefix hash: 54c42f4d869f88f9fdc436644565fe4cd0e9124d54a69630ba8379515440a6f1
Tx public key: da9ab85b9a44c9880edc5e5d486c07261f931f831f991da519c85b2281dce879
Timestamp: 1731305065 Timestamp [UCT]: 2024-11-11 06:04:25 Age [y:d:h:m:s]: 00:167:18:07:58
Block: 1151184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119751 RingCT/type: yes/0
Extra: 01da9ab85b9a44c9880edc5e5d486c07261f931f831f991da519c85b2281dce879021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f949fd9fa74d385e85d06f4568489f0d3b72a2ef5994dc41e0e4348cc87102f 0.600000000000 1636669 of 15

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": 1151194, "vin": [ { "gen": { "height": 1151184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f949fd9fa74d385e85d06f4568489f0d3b72a2ef5994dc41e0e4348cc87102f" } } ], "extra": [ 1, 218, 154, 184, 91, 154, 68, 201, 136, 14, 220, 94, 93, 72, 108, 7, 38, 31, 147, 31, 131, 31, 153, 29, 165, 25, 200, 91, 34, 129, 220, 232, 121, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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