Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa210acf628684e1967fb858140d2fb063775b07a15df3e72c1fbb254146b53a

Tx prefix hash: 564f33c61549975c927749dfd3821681c40b03f35ba833b8dad63bb8746d18c7
Tx public key: 946fecefe2f681d6bfd55997598673b3571ed42e3a1d841dd754264bc371086f
Timestamp: 1695936715 Timestamp [UCT]: 2023-09-28 21:31:55 Age [y:d:h:m:s]: 01:182:10:46:05
Block: 858260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391445 RingCT/type: yes/0
Extra: 01946fecefe2f681d6bfd55997598673b3571ed42e3a1d841dd754264bc371086f021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.879484893000 dcy

stealth address amount amount idx
00: ae73b87d727f2e043eb82fae946dae52e5eab17abda1ab37a0c7621e75e19dc0 0.879484893000 1312428 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": 858270, "vin": [ { "gen": { "height": 858260 } } ], "vout": [ { "amount": 879484893, "target": { "key": "ae73b87d727f2e043eb82fae946dae52e5eab17abda1ab37a0c7621e75e19dc0" } } ], "extra": [ 1, 148, 111, 236, 239, 226, 246, 129, 214, 191, 213, 89, 151, 89, 134, 115, 179, 87, 30, 212, 46, 58, 29, 132, 29, 215, 84, 38, 75, 195, 113, 8, 111, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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