Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f3360cdec9c310b33b35ec3b6de79bef1784d839eeaf4d97a109702711304f

Tx prefix hash: 3b93475e31e754647457cbaa6a8f80a1c243efc62ee97b567a61c02771763015
Tx public key: f18d4e59a81fa364a836d5d82f4a523a05486d3826aaea7982def899b4acc744
Timestamp: 1747999726 Timestamp [UCT]: 2025-05-23 11:28:46 Age [y:d:h:m:s]: 00:252:17:01:12
Block: 1289152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178218 RingCT/type: yes/0
Extra: 01f18d4e59a81fa364a836d5d82f4a523a05486d3826aaea7982def899b4acc7440211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 783d48dcfbd4c9865e986c438cd06eb6b61294837c257bbac5aaf6e5c15a1050 0.600000000000 1776619 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": 1289162, "vin": [ { "gen": { "height": 1289152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "783d48dcfbd4c9865e986c438cd06eb6b61294837c257bbac5aaf6e5c15a1050" } } ], "extra": [ 1, 241, 141, 78, 89, 168, 31, 163, 100, 168, 54, 213, 216, 47, 74, 82, 58, 5, 72, 109, 56, 38, 170, 234, 121, 130, 222, 248, 153, 180, 172, 199, 68, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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