Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ec46b48250dbc859ea28ff3e05d97530e7d46d35b83296dd2969efc64c8fe0

Tx prefix hash: 492f47a97ed8ba9e111fc8dda1ecfd3da1ee2665a2e9ff77de7f05181dc8bfe9
Tx public key: 9f96b21b37d6c2cebe3a24af5ae127106e7a1b577e8b714590193fef6bb3e6af
Timestamp: 1759202207 Timestamp [UCT]: 2025-09-30 03:16:47 Age [y:d:h:m:s]: 00:094:01:40:59
Block: 1379437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67372 RingCT/type: yes/0
Extra: 019f96b21b37d6c2cebe3a24af5ae127106e7a1b577e8b714590193fef6bb3e6af02110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bad3c80df14468811b2aee6f700d21751c47aa914e5458eabb6bbbb96bab7e41 0.600000000000 1867534 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": 1379447, "vin": [ { "gen": { "height": 1379437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bad3c80df14468811b2aee6f700d21751c47aa914e5458eabb6bbbb96bab7e41" } } ], "extra": [ 1, 159, 150, 178, 27, 55, 214, 194, 206, 190, 58, 36, 175, 90, 225, 39, 16, 110, 122, 27, 87, 126, 139, 113, 69, 144, 25, 63, 239, 107, 179, 230, 175, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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