Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 695d2765dcf1660500d2fd06cef34dcc4b8dc843a2b4464c02d680f135538ec3

Tx prefix hash: d3d9c381bb5410d12ef4fbef4cde3b4c7378b8777555cefbb6d6f896e38f946a
Tx public key: dc9674a705acb3480fb91d426a23811a5defda42cf56a7addb36b958249e921c
Timestamp: 1704829442 Timestamp [UCT]: 2024-01-09 19:44:02 Age [y:d:h:m:s]: 01:016:03:10:45
Block: 931772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272819 RingCT/type: yes/0
Extra: 01dc9674a705acb3480fb91d426a23811a5defda42cf56a7addb36b958249e921c0211000000029da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d314f650d4c349879e41eb3a63206063a05b566258b58bbce085f8587c6e9e03 0.600000000000 1389676 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": 931782, "vin": [ { "gen": { "height": 931772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d314f650d4c349879e41eb3a63206063a05b566258b58bbce085f8587c6e9e03" } } ], "extra": [ 1, 220, 150, 116, 167, 5, 172, 179, 72, 15, 185, 29, 66, 106, 35, 129, 26, 93, 239, 218, 66, 207, 86, 167, 173, 219, 54, 185, 88, 36, 158, 146, 28, 2, 17, 0, 0, 0, 2, 157, 168, 225, 52, 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