Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1ddb60a92d19c5b25684342e7e2672b74f9141ad92f8aeec21a1dd4203b37d8

Tx prefix hash: b4d07384d2b644ed11e3c8e285c4456c198e767bd70a4a983fddcde1b6f45f39
Tx public key: 0585f89f9c9f35a542624b53d39698ce354726450eff7616a0337a853e0f69eb
Timestamp: 1708244573 Timestamp [UCT]: 2024-02-18 08:22:53 Age [y:d:h:m:s]: 01:040:06:42:08
Block: 960095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289815 RingCT/type: yes/0
Extra: 010585f89f9c9f35a542624b53d39698ce354726450eff7616a0337a853e0f69eb0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e372bcc91a20f57ef815780a4324d76c26f5f1774760c2e2f74c955cb3855b1f 0.600000000000 1419654 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": 960105, "vin": [ { "gen": { "height": 960095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e372bcc91a20f57ef815780a4324d76c26f5f1774760c2e2f74c955cb3855b1f" } } ], "extra": [ 1, 5, 133, 248, 159, 156, 159, 53, 165, 66, 98, 75, 83, 211, 150, 152, 206, 53, 71, 38, 69, 14, 255, 118, 22, 160, 51, 122, 133, 62, 15, 105, 235, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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