← previous blocknext block →recent activity

Analyzing

Block #88,088,825

22 transactions · 19 stateful · 2026-07-16 07:50:01 UTC

Parallelism

86/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,088,825  ·  22 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x1136ab0f…f1da

0x065c9d…c394

6 touches
3 conflicts

0x2b5101ac…090b

0x34b655…2a6f

6 touches
3 conflicts

0xb550abea…2729

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity