← previous blocknext block →recent activity

Analyzing

Block #88,157,246

22 transactions · 20 stateful · 2026-07-16 15:27:56 UTC

Parallelism

64/100

Blocked

40%

Avg conflicts / tx

1.23

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #88,157,246  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x8d989c17…e984

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x69a45f39…39aa

0x34b655…2a6f

6 touches
3 conflicts

0x9465204c…bf37

0x34b655…2a6f

6 touches
3 conflicts

0x99af85c8…6cab

0x34b655…2a6f

6 touches
3 conflicts

0xbb4fd99a…afa6

0x34b655…2a6f

6 touches
3 conflicts

0x7a2c83a3…a29a

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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

15 conflicts on slot 0x8d989c177f…b7e984

← previous block·next block →recent activity