← previous blocknext block →recent activity
Analyzing
Block #87,753,441
17 transactions · 14 stateful · 2026-07-14 18:26:47 UTC
Parallelism
59/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,753,441 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w38w411w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc616f7f…6178
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x648bb928…97f2
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x59a5e379…ad8e
0x34b655…2a6f
6 touches
3 conflicts
0x59a5e379…ad8f
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
6 conflicts on slot 0xcc616f7f2b…a56178
Audit this contract →
← previous block·next block →recent activity