Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f2ea5f27565be0ef46eb7906cf9d690151cb914fff6333b16a7b4b382f4d866

Tx prefix hash: a463e565be7a0c6a070617411b1c4665b405f6c702b5b69480e68db114efdc6d
Tx public key: fc594e7beed14f1dac7bf714a938b07ceba5411423ac12e9a6e8b5e7c1ba79be
Timestamp: 1698304303 Timestamp [UCT]: 2023-10-26 07:11:43 Age [y:d:h:m:s]: 01:191:21:24:05
Block: 877911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398145 RingCT/type: yes/0
Extra: 01fc594e7beed14f1dac7bf714a938b07ceba5411423ac12e9a6e8b5e7c1ba79be0211000000064b8f5122000000000000000000

1 output(s) for total of 0.757035829000 dcy

stealth address amount amount idx
00: 39a37df843452fff63921d506c73db6add7b9e14f2a3d4e8ea964e819a886cae 0.757035829000 1333309 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": 877921, "vin": [ { "gen": { "height": 877911 } } ], "vout": [ { "amount": 757035829, "target": { "key": "39a37df843452fff63921d506c73db6add7b9e14f2a3d4e8ea964e819a886cae" } } ], "extra": [ 1, 252, 89, 78, 123, 238, 209, 79, 29, 172, 123, 247, 20, 169, 56, 176, 124, 235, 165, 65, 20, 35, 172, 18, 233, 166, 232, 181, 231, 193, 186, 121, 190, 2, 17, 0, 0, 0, 6, 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