Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93c09967116edf19ca9641925974ae8e5a380cbda812c66effdedff01babc451

Tx prefix hash: e7e78867b809ae92b9b420e897f91939d4a015d7495d98a727f34c4f26e4a473
Tx public key: ccff2c9a0159aa955f1c2314653fd21e31c3517bcc307fcc084e55dace440da5
Timestamp: 1729205836 Timestamp [UCT]: 2024-10-17 22:57:16 Age [y:d:h:m:s]: 00:157:19:05:42
Block: 1133875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112540 RingCT/type: yes/0
Extra: 01ccff2c9a0159aa955f1c2314653fd21e31c3517bcc307fcc084e55dace440da502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0966187f42e3f1077728a5d568e6dac8a56d44b6c75ae93c82c460d3324b8fa1 0.600000000000 1617088 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": 1133885, "vin": [ { "gen": { "height": 1133875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0966187f42e3f1077728a5d568e6dac8a56d44b6c75ae93c82c460d3324b8fa1" } } ], "extra": [ 1, 204, 255, 44, 154, 1, 89, 170, 149, 95, 28, 35, 20, 101, 63, 210, 30, 49, 195, 81, 123, 204, 48, 127, 204, 8, 78, 85, 218, 206, 68, 13, 165, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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