Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2ebc3bfa429f532ac367237802b62e414c4d7315e8d2ec99bd421a985e556d9

Tx prefix hash: 76d2ccaef37be3476529f24f7c0b00813ff80f3ecba037cc012772d3d05a9fb5
Tx public key: 18406684ffd1cc9a925143d19675859aa7e4f5e9d64c88574a7c84f4a4f76311
Timestamp: 1725222348 Timestamp [UCT]: 2024-09-01 20:25:48 Age [y:d:h:m:s]: 01:059:09:36:12
Block: 1100853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300884 RingCT/type: yes/0
Extra: 0118406684ffd1cc9a925143d19675859aa7e4f5e9d64c88574a7c84f4a4f76311021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aa36916106242667d813fc241e001731e841f0f441613c4ef8070d7f22b4951 0.600000000000 1576834 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": 1100863, "vin": [ { "gen": { "height": 1100853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa36916106242667d813fc241e001731e841f0f441613c4ef8070d7f22b4951" } } ], "extra": [ 1, 24, 64, 102, 132, 255, 209, 204, 154, 146, 81, 67, 209, 150, 117, 133, 154, 167, 228, 245, 233, 214, 76, 136, 87, 74, 124, 132, 244, 164, 247, 99, 17, 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