Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2163596b4ba67f56784add3ed232702a42ebe666a6e4044d39bb8c9ca0b947e

Tx prefix hash: dc5ebfffaef157cb0dcf64905e12c52e3f4a6a72a5ac693501307a60f3744c49
Tx public key: cb31c5b0b8590dbfafd293a1becb9633f46abe27f0eddb5e90ee97c802f22b45
Timestamp: 1734595402 Timestamp [UCT]: 2024-12-19 08:03:22 Age [y:d:h:m:s]: 00:143:08:51:18
Block: 1178464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102254 RingCT/type: yes/0
Extra: 01cb31c5b0b8590dbfafd293a1becb9633f46abe27f0eddb5e90ee97c802f22b45021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5f6d11c2821647639b1f0bc97ad9a20491c193958deea1b54ff9205d923b08 0.600000000000 1664851 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": 1178474, "vin": [ { "gen": { "height": 1178464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5f6d11c2821647639b1f0bc97ad9a20491c193958deea1b54ff9205d923b08" } } ], "extra": [ 1, 203, 49, 197, 176, 184, 89, 13, 191, 175, 210, 147, 161, 190, 203, 150, 51, 244, 106, 190, 39, 240, 237, 219, 94, 144, 238, 151, 200, 2, 242, 43, 69, 2, 17, 0, 0, 0, 3, 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