Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e49503a9a245c87848639e344d3bc980318bb5dd8e484d3a5d43e05bae074bc1

Tx prefix hash: afcde2aed9e99c320f5bf846a3a5dbe0d3394a7f56d3a7b752b035553bb7175a
Tx public key: 3783db1b1c444f621a57f451d124db0fcc40152104b6ac0583c0f7a5577f0630
Timestamp: 1763494374 Timestamp [UCT]: 2025-11-18 19:32:54 Age [y:d:h:m:s]: 00:009:13:48:40
Block: 1415014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6863 RingCT/type: yes/0
Extra: 013783db1b1c444f621a57f451d124db0fcc40152104b6ac0583c0f7a5577f0630021100000004fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b913c6fde8feb67f4f654a3904e4bfa98a497790564cf80b76027cbfae881228 0.600000000000 1903507 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": 1415024, "vin": [ { "gen": { "height": 1415014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b913c6fde8feb67f4f654a3904e4bfa98a497790564cf80b76027cbfae881228" } } ], "extra": [ 1, 55, 131, 219, 27, 28, 68, 79, 98, 26, 87, 244, 81, 209, 36, 219, 15, 204, 64, 21, 33, 4, 182, 172, 5, 131, 192, 247, 165, 87, 127, 6, 48, 2, 17, 0, 0, 0, 4, 251, 143, 208, 137, 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