Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1d5f9ab57aaa28a24720e809ed4342a30d8450aed98f0af81ef5e599bdd39a8

Tx prefix hash: d983b3405cd2b20175de6f458837a951c0bac0bd126426fb9d5942c01d586761
Tx public key: e5d16e35e9b7baf666654faf8841d1dc67e752bcf79123f50080d5a01ad10ae7
Timestamp: 1750863462 Timestamp [UCT]: 2025-06-25 14:57:42 Age [y:d:h:m:s]: 00:141:17:54:44
Block: 1312582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99258 RingCT/type: yes/0
Extra: 01e5d16e35e9b7baf666654faf8841d1dc67e752bcf79123f50080d5a01ad10ae7021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0111a5d4114944de7ca835f24e3ce912ad0365b910812a2982fc782d889df224 0.600000000000 1800215 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": 1312592, "vin": [ { "gen": { "height": 1312582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0111a5d4114944de7ca835f24e3ce912ad0365b910812a2982fc782d889df224" } } ], "extra": [ 1, 229, 209, 110, 53, 233, 183, 186, 246, 102, 101, 79, 175, 136, 65, 209, 220, 103, 231, 82, 188, 247, 145, 35, 245, 0, 128, 213, 160, 26, 209, 10, 231, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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