Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4435c3e5b1fcc8a89d630a4ee4ea9c752b8c2bcde8c2cc6834df0e320aaf5d5c

Tx prefix hash: 594f533c36835c6536b1d2e42fece3aebfe9422c853d9d59b7a88cb2d7411cd4
Tx public key: e513f30be5cda967fe2e9ea0c202360444df385fc9c1671278d321919618c9b7
Timestamp: 1722570946 Timestamp [UCT]: 2024-08-02 03:55:46 Age [y:d:h:m:s]: 00:250:13:57:23
Block: 1078863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178997 RingCT/type: yes/0
Extra: 01e513f30be5cda967fe2e9ea0c202360444df385fc9c1671278d321919618c9b702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1d91f6996d38908c0d4a9cdcab0be876c86a3e251c7ae3c2d50f1182d888f3a 0.600000000000 1551574 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": 1078873, "vin": [ { "gen": { "height": 1078863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1d91f6996d38908c0d4a9cdcab0be876c86a3e251c7ae3c2d50f1182d888f3a" } } ], "extra": [ 1, 229, 19, 243, 11, 229, 205, 169, 103, 254, 46, 158, 160, 194, 2, 54, 4, 68, 223, 56, 95, 201, 193, 103, 18, 120, 211, 33, 145, 150, 24, 201, 183, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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