Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b5e5675c16f8836bf90a67990cb742d59476e67a6ed99fa0586acbc5088f40b

Tx prefix hash: e9cf39e454f31f84207b29f70cbb9ba6988a5b9dca1a2800ec6cdb94cf5c1212
Tx public key: cc238cc400014a91ba9de49dd823a21fee5f0ca4151852c90b7a4b4dab2c2c49
Timestamp: 1722151350 Timestamp [UCT]: 2024-07-28 07:22:30 Age [y:d:h:m:s]: 00:252:01:50:52
Block: 1075387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180066 RingCT/type: yes/0
Extra: 01cc238cc400014a91ba9de49dd823a21fee5f0ca4151852c90b7a4b4dab2c2c49021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ef121847b60917db6864e12409ecc65ba6d23d621bf16aa6dca9c9da8fe9448 0.600000000000 1547912 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": 1075397, "vin": [ { "gen": { "height": 1075387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ef121847b60917db6864e12409ecc65ba6d23d621bf16aa6dca9c9da8fe9448" } } ], "extra": [ 1, 204, 35, 140, 196, 0, 1, 74, 145, 186, 157, 228, 157, 216, 35, 162, 31, 238, 95, 12, 164, 21, 24, 82, 201, 11, 122, 75, 77, 171, 44, 44, 73, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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