Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75a9f3341df81c161620fc4879f8846cb43ef9fc1d4ad02d802da5e61a3ab98c

Tx prefix hash: 7d91ac0a3250d06ae3ef59008936ad2111c8bb40ec73f5655ea07b2213261b6d
Tx public key: 37e8eef3839b4b1c0fe221ee0f030a5a8d0abc9bb69b561af416eaa528e3cc29
Timestamp: 1709035810 Timestamp [UCT]: 2024-02-27 12:10:10 Age [y:d:h:m:s]: 00:207:00:31:14
Block: 966667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148287 RingCT/type: yes/0
Extra: 0137e8eef3839b4b1c0fe221ee0f030a5a8d0abc9bb69b561af416eaa528e3cc2902110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e46cfbb7ca6506cf9fec7d894b4b8b0752ba8f40b5d3a36df6cf7ce59e4a4e74 0.600000000000 1426434 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": 966677, "vin": [ { "gen": { "height": 966667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e46cfbb7ca6506cf9fec7d894b4b8b0752ba8f40b5d3a36df6cf7ce59e4a4e74" } } ], "extra": [ 1, 55, 232, 238, 243, 131, 155, 75, 28, 15, 226, 33, 238, 15, 3, 10, 90, 141, 10, 188, 155, 182, 155, 86, 26, 244, 22, 234, 165, 40, 227, 204, 41, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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