Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bc9ba7c02c380c674ce67a2efab75f46dabb91c76702b082db363baee58ad64

Tx prefix hash: 9132cb57879df82196678214a791ae0d49f76f06efc993b6c2b167950924eb28
Tx public key: 693a0eb67d1bf55703834d0967b19ae3681b6f17ca5ac7a5c7f5a1f9115ac1a0
Timestamp: 1698690770 Timestamp [UCT]: 2023-10-30 18:32:50 Age [y:d:h:m:s]: 01:150:15:55:35
Block: 881110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368662 RingCT/type: yes/0
Extra: 01693a0eb67d1bf55703834d0967b19ae3681b6f17ca5ac7a5c7f5a1f9115ac1a00211000000054b8f5122000000000000000000

1 output(s) for total of 0.738782866000 dcy

stealth address amount amount idx
00: 53ce81e9c2de904eda1c7848fd961cf99b0b109439d339ccd90129320170c00a 0.738782866000 1336686 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": 881120, "vin": [ { "gen": { "height": 881110 } } ], "vout": [ { "amount": 738782866, "target": { "key": "53ce81e9c2de904eda1c7848fd961cf99b0b109439d339ccd90129320170c00a" } } ], "extra": [ 1, 105, 58, 14, 182, 125, 27, 245, 87, 3, 131, 77, 9, 103, 177, 154, 227, 104, 27, 111, 23, 202, 90, 199, 165, 199, 245, 161, 249, 17, 90, 193, 160, 2, 17, 0, 0, 0, 5, 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