← previous blocknext block →recent activity

Analyzing

Block #87,902,273

12 transactions · 11 stateful · 2026-07-15 11:02:19 UTC

Parallelism

75/100

Blocked

45%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,902,273  ·  12 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

0xe40c96f3…9ce4

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x1928db9c…6ea9

0x34b655…2a6f

4 touches
1 conflict

0x1f8e77cc…4646

0x34b655…2a6f

4 touches
1 conflict

0x2571f435…11bd

0x34b655…2a6f

4 touches
1 conflict

0x5d7f309d…5145

0x34b655…2a6f

4 touches
1 conflict

0x5dc93134…aaef

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 0xe40c96f301…1b9ce4

← previous block·next block →recent activity