Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ed5d35420fc7392c474bc4aab9b1f1a1c7c0071be467994b3097178dc1c1732

Tx prefix hash: 719fdb2c4d368169de7622559bc1153812da0f1af86c08535985dea2c45af909
Tx public key: b7be9316e91f65868b3d670c5c3b4f69f1c99e12ebb3465bbe335354aec52c4c
Timestamp: 1681426619 Timestamp [UCT]: 2023-04-13 22:56:59 Age [y:d:h:m:s]: 01:273:08:04:28
Block: 738006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456860 RingCT/type: yes/0
Extra: 01b7be9316e91f65868b3d670c5c3b4f69f1c99e12ebb3465bbe335354aec52c4c0211000000025029cbac000000000000000000

1 output(s) for total of 2.201303793000 dcy

stealth address amount amount idx
00: 8bb96209bfc1cb9b3fe54be4d15db396a7df8209f561b2b932f079c995e306f8 2.201303793000 1184639 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": 738016, "vin": [ { "gen": { "height": 738006 } } ], "vout": [ { "amount": 2201303793, "target": { "key": "8bb96209bfc1cb9b3fe54be4d15db396a7df8209f561b2b932f079c995e306f8" } } ], "extra": [ 1, 183, 190, 147, 22, 233, 31, 101, 134, 139, 61, 103, 12, 92, 59, 79, 105, 241, 201, 158, 18, 235, 179, 70, 91, 190, 51, 83, 84, 174, 197, 44, 76, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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