Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b050d19f998078ed7a85882fcae464f3bdc67c39b23b9349f1be5fec6daab85

Tx prefix hash: 5ad75a41cb3ab99f855cd17af9af4e389880abe4c948bb3192de3bfbfd05d62c
Tx public key: ddf8666701a5271d4a4f9f9265b1fbf50a8ee6b76d724eaee4930b1a1713e584
Timestamp: 1752153555 Timestamp [UCT]: 2025-07-10 13:19:15 Age [y:d:h:m:s]: 00:182:05:35:27
Block: 1322648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128871 RingCT/type: yes/0
Extra: 01ddf8666701a5271d4a4f9f9265b1fbf50a8ee6b76d724eaee4930b1a1713e58402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c23ba39fa2dc67df5b5afa35f562af6abe5f73e5ca413a247814a75857a702e5 0.600000000000 1810379 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": 1322658, "vin": [ { "gen": { "height": 1322648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c23ba39fa2dc67df5b5afa35f562af6abe5f73e5ca413a247814a75857a702e5" } } ], "extra": [ 1, 221, 248, 102, 103, 1, 165, 39, 29, 74, 79, 159, 146, 101, 177, 251, 245, 10, 142, 230, 183, 109, 114, 78, 174, 228, 147, 11, 26, 23, 19, 229, 132, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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