Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e60bc3d1bf7a7f69abb9efa7c410c150b0bc06f306eb94b21c26d5415d7c6afc

Tx prefix hash: 940b82591e6b0eb6dc8822198b961386853bff1d5ad62f5a648a0af3a39f534d
Tx public key: 8e3c2826bc9358beae6dcc011263258469c258fe8b2565a95179a009aab964d8
Timestamp: 1736561485 Timestamp [UCT]: 2025-01-11 02:11:25 Age [y:d:h:m:s]: 00:159:15:10:04
Block: 1194710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113794 RingCT/type: yes/0
Extra: 018e3c2826bc9358beae6dcc011263258469c258fe8b2565a95179a009aab964d802110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 609c1fb6311e168b3dfac1832ae3d3f875eb68eb57832d2fde2b4b61c6711b34 0.600000000000 1681287 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": 1194720, "vin": [ { "gen": { "height": 1194710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "609c1fb6311e168b3dfac1832ae3d3f875eb68eb57832d2fde2b4b61c6711b34" } } ], "extra": [ 1, 142, 60, 40, 38, 188, 147, 88, 190, 174, 109, 204, 1, 18, 99, 37, 132, 105, 194, 88, 254, 139, 37, 101, 169, 81, 121, 160, 9, 170, 185, 100, 216, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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