Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 021815e3b81bcc5d4435a10730d26093d35169ade7b81c41ec36eb2dc71b2790

Tx prefix hash: 6ae8fdc585647962284d646218dcaa7bc3e4adf94a50c1d339a1e86006916137
Tx public key: c409a9784ae624ed9b6dda979d57a9a69f09a545cd1d92cd832d7f7ee36e15e2
Timestamp: 1764342666 Timestamp [UCT]: 2025-11-28 15:11:06 Age [y:d:h:m:s]: 00:064:20:44:51
Block: 1422049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46258 RingCT/type: yes/0
Extra: 01c409a9784ae624ed9b6dda979d57a9a69f09a545cd1d92cd832d7f7ee36e15e202110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2ca03ecd6a2ba434437415955f52d9186d49d4efa2f44f5755f6a22138ae48d 0.600000000000 1910614 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": 1422059, "vin": [ { "gen": { "height": 1422049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2ca03ecd6a2ba434437415955f52d9186d49d4efa2f44f5755f6a22138ae48d" } } ], "extra": [ 1, 196, 9, 169, 120, 74, 230, 36, 237, 155, 109, 218, 151, 157, 87, 169, 166, 159, 9, 165, 69, 205, 29, 146, 205, 131, 45, 127, 126, 227, 110, 21, 226, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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