Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38317dcada3c62de5a83c46af5d0e7839669ddaaa5de6124b5f9a6661e26d38e

Tx prefix hash: 38ee3f91df5dc31e89fb99d68e9a57ad4dcdd8cb5029211aaaf5f300bc86a9b0
Tx public key: ea6ddcba232da978e7d6f6977365162e52b6fda090ade0f438c15cf0a447de90
Timestamp: 1730337632 Timestamp [UCT]: 2024-10-31 01:20:32 Age [y:d:h:m:s]: 00:143:03:59:15
Block: 1143170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102165 RingCT/type: yes/0
Extra: 01ea6ddcba232da978e7d6f6977365162e52b6fda090ade0f438c15cf0a447de9002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4acfbbc2c1cdb67b216f01e530e1dc371b39459948fc2ce7e967df26440056f 0.600000000000 1627033 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": 1143180, "vin": [ { "gen": { "height": 1143170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4acfbbc2c1cdb67b216f01e530e1dc371b39459948fc2ce7e967df26440056f" } } ], "extra": [ 1, 234, 109, 220, 186, 35, 45, 169, 120, 231, 214, 246, 151, 115, 101, 22, 46, 82, 182, 253, 160, 144, 173, 224, 244, 56, 193, 92, 240, 164, 71, 222, 144, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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