← previous blocknext block →recent activity
Analyzing
Block #87,317,563
15 transactions · 13 stateful · 2026-07-12 17:50:50 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,317,563 · 15 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
1w02w14w05w16w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc893169b…6d75
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
6 touches
3 conflicts
0x93459a00…1fc2
0x34b655…2a6f
6 touches
3 conflicts
0xe181f491…f4e3
0x34b655…2a6f
6 touches
3 conflicts
0x3674075e…02b7
0x34b655…2a6f
4 touches
1 conflict
0x451f5977…7300
0x34b655…2a6f
4 touches
1 conflict
0x4797cebc…5c38
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 0xc893169bf9…326d75
Audit this contract →
← previous block·next block →recent activity