Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f984afd43b75732f8e25699e6be9287226e260a43e078b06a293db33a76439ac

Tx prefix hash: b10c2c4ee53ae31bdde264880a6fb063258b3de9c3b646405abd1e1a81c04300
Tx public key: 3f30c8246704312f71715122a39fb2c29cb179b9534b76200c77faaaaa78d8ae
Timestamp: 1708334034 Timestamp [UCT]: 2024-02-19 09:13:54 Age [y:d:h:m:s]: 00:323:01:59:02
Block: 960837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231286 RingCT/type: yes/0
Extra: 013f30c8246704312f71715122a39fb2c29cb179b9534b76200c77faaaaa78d8ae0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e25d5e2cc369250a699b9e57f80a6d5c3690e6cdf34f905b5943f1901a5a6046 0.600000000000 1420424 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": 960847, "vin": [ { "gen": { "height": 960837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e25d5e2cc369250a699b9e57f80a6d5c3690e6cdf34f905b5943f1901a5a6046" } } ], "extra": [ 1, 63, 48, 200, 36, 103, 4, 49, 47, 113, 113, 81, 34, 163, 159, 178, 194, 156, 177, 121, 185, 83, 75, 118, 32, 12, 119, 250, 170, 170, 120, 216, 174, 2, 17, 0, 0, 0, 1, 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