← previous blocknext block →recent activity
Analyzing
Block #87,262,879
12 transactions · 12 stateful · 2026-07-12 11:45:14 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,262,879 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e859a7c…d0f2
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xb2a25bac…c741
0x34b655…2a6f
6 touches
3 conflicts
0x2bc13458…e6d8
0x34b655…2a6f
4 touches
1 conflict
0x40080907…45cc
0x34b655…2a6f
4 touches
1 conflict
0x49e0713b…0e69
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
6 conflicts on slot 0x6e859a7cbe…32d0f2
Audit this contract →
← previous block·next block →recent activity