← previous blocknext block →recent activity
Analyzing
Block #87,918,340
30 transactions · 25 stateful · 2026-07-15 12:49:45 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.57
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,918,340 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w310w413w214w315w417w120w525w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7545436b…012e
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8218911e…3bed
0x34b655…2a6f
6 touches
3 conflicts
0x3559c176…9fe1
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity