← previous blocknext block →recent activity
Analyzing
Block #87,330,605
11 transactions · 9 stateful · 2026-07-12 19:18:04 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,330,605 · 11 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
2w05w06w17w18w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x680ca7d7…2df4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x4bfbd222…8aa7
0x34b655…2a6f
4 touches
1 conflict
0x6638e124…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x80bf58f2…be95
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x680ca7d7a6…292df4
Audit this contract →
← previous block·next block →recent activity