Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2467c04056cf7451b6ccb7442ad8e0dc6a60c617dd66f4e2f37405e61f4ed80b

Tx prefix hash: 37889e49e7a48d4ee92f509c3109d38f1d6c1ecb1a142c0edcd19dcee75377dd
Tx public key: ed6726510717e63ae878d1271224f208a8662823b55d782e1b5a5450ae8886a9
Timestamp: 1722540998 Timestamp [UCT]: 2024-08-01 19:36:38 Age [y:d:h:m:s]: 00:309:12:27:28
Block: 1078616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221165 RingCT/type: yes/0
Extra: 01ed6726510717e63ae878d1271224f208a8662823b55d782e1b5a5450ae8886a9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09e6b18fe334851a65763149d3ed20487b69f4ee332a9c5f92e99d9b78d2069a 0.600000000000 1551221 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": 1078626, "vin": [ { "gen": { "height": 1078616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09e6b18fe334851a65763149d3ed20487b69f4ee332a9c5f92e99d9b78d2069a" } } ], "extra": [ 1, 237, 103, 38, 81, 7, 23, 230, 58, 232, 120, 209, 39, 18, 36, 242, 8, 168, 102, 40, 35, 181, 93, 120, 46, 27, 90, 84, 80, 174, 136, 134, 169, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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