Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e49a401ee31d422c1a061f23768037ab5252226a7dae15503fd81723b39d8829

Tx prefix hash: f0be705007c8f3df94e6f98cd95f2332985cba0d464f7027b40eb96c24c70c82
Tx public key: 038cb0b23bde537625a6073d83a1cc4a4e1e997977cfbf460dd0c37208d55b52
Timestamp: 1750709614 Timestamp [UCT]: 2025-06-23 20:13:34 Age [y:d:h:m:s]: 00:148:03:01:03
Block: 1311329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103796 RingCT/type: yes/0
Extra: 01038cb0b23bde537625a6073d83a1cc4a4e1e997977cfbf460dd0c37208d55b5202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6745c65e5f021516599d18b11beb2f0e809eda00f6c1ed1e2e92d6e4f605dc0b 0.600000000000 1798956 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": 1311339, "vin": [ { "gen": { "height": 1311329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6745c65e5f021516599d18b11beb2f0e809eda00f6c1ed1e2e92d6e4f605dc0b" } } ], "extra": [ 1, 3, 140, 176, 178, 59, 222, 83, 118, 37, 166, 7, 61, 131, 161, 204, 74, 78, 30, 153, 121, 119, 207, 191, 70, 13, 208, 195, 114, 8, 213, 91, 82, 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