Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77edcb749b4f900c53bc31f7be373e67e9e1349c2116abaf8485c5a059644416

Tx prefix hash: 0302e94dafac261a477629194fadcb4a5ec136897369d76d52f176be0e2047b0
Tx public key: f7efd85a96215fcfafbe7aaf477484809fce4f4f975eefff757ad3e7c73ed2b6
Timestamp: 1696039628 Timestamp [UCT]: 2023-09-30 02:07:08 Age [y:d:h:m:s]: 01:048:02:25:37
Block: 859115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295619 RingCT/type: yes/0
Extra: 01f7efd85a96215fcfafbe7aaf477484809fce4f4f975eefff757ad3e7c73ed2b60211000000034b8f5122000000000000000000

1 output(s) for total of 0.873766546000 dcy

stealth address amount amount idx
00: 5f13c781001250bd8ddcab4c75d2a118961610472ea5788b33c5814394cb68e5 0.873766546000 1313325 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": 859125, "vin": [ { "gen": { "height": 859115 } } ], "vout": [ { "amount": 873766546, "target": { "key": "5f13c781001250bd8ddcab4c75d2a118961610472ea5788b33c5814394cb68e5" } } ], "extra": [ 1, 247, 239, 216, 90, 150, 33, 95, 207, 175, 190, 122, 175, 71, 116, 132, 128, 159, 206, 79, 79, 151, 94, 239, 255, 117, 122, 211, 231, 199, 62, 210, 182, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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