Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de30fa16b5c5733c31707bd566ed0ee2c5b9f1fadb6045f1d6b53b587da6fbed

Tx prefix hash: 558c299cfd29cb038d48d4fd572ccfce792e546a98551d404009633172564e88
Tx public key: d65e72067a5b3eece08b0b79c9ade247f7b82225b241d196bb4b41a9c45dc71e
Timestamp: 1702026027 Timestamp [UCT]: 2023-12-08 09:00:27 Age [y:d:h:m:s]: 01:124:07:07:49
Block: 908541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349982 RingCT/type: yes/0
Extra: 01d65e72067a5b3eece08b0b79c9ade247f7b82225b241d196bb4b41a9c45dc71e02110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52ae64ebbd0c7293afa0eb8e93c9d359b30a3bc4526c94950f8cb852b2f4294d 0.600000000000 1365574 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": 908551, "vin": [ { "gen": { "height": 908541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52ae64ebbd0c7293afa0eb8e93c9d359b30a3bc4526c94950f8cb852b2f4294d" } } ], "extra": [ 1, 214, 94, 114, 6, 122, 91, 62, 236, 224, 139, 11, 121, 201, 173, 226, 71, 247, 184, 34, 37, 178, 65, 209, 150, 187, 75, 65, 169, 196, 93, 199, 30, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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