← previous blocknext block →recent activity

Analyzing

Block #86,957,937

24 transactions · 19 stateful · 2026-07-11 01:46:33 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,957,937  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3336de97…1806

0x065c9d…c394

5 touches
3 conflicts

0x238a359d…f9f5

0x34b655…2a6f

4 touches
1 conflict

0x2b7950c1…2342

0x34b655…2a6f

4 touches
1 conflict

0x3e0072a8…95fc

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x9b215661…7305

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: MarginAccount

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity