← previous blocknext block →recent activity

Analyzing

Block #88,351,696

17 transactions · 15 stateful · 2026-07-17 13:08:51 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,351,696  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x02991b41…19e6

0x34b655…2a6f

6 touches
3 conflicts

0xec152baf…a069

0x34b655…2a6f

6 touches
3 conflicts

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x366748e9…1282

0x34b655…2a6f

4 touches
1 conflict

0x436d7385…abd0

0x34b655…2a6f

4 touches
1 conflict

0x446c9ed6…c25c

0x34b655…2a6f

4 touches
1 conflict

0x4c789650…7577

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: Perpl

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity