← previous blocknext block →recent activity

Analyzing

Block #88,353,023

24 transactions · 20 stateful · 2026-07-17 13:17:43 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,353,023  ·  24 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

0xfb874a6c…caa0

0x34b655…2a6f

6 touches
3 conflicts

0x3b0a8356…a2b6

0x34b655…2a6f

4 touches
1 conflict

0x6b7377f5…7ea7

0x34b655…2a6f

4 touches
1 conflict

0x6e1cd42e…1f23

0x34b655…2a6f

4 touches
1 conflict

0x7300ca0a…a397

0x34b655…2a6f

4 touches
1 conflict

0x7cf35280…a881

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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