← previous blocknext block →recent activity
Analyzing
Block #87,258,122
12 transactions · 11 stateful · 2026-07-12 11:13:26 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,258,122 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16ba1d53…4480
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0c53719e…0366
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x78346476…4311
0x34b655…2a6f
4 touches
1 conflict
0xf982b915…898b
0x34b655…2a6f
4 touches
1 conflict
0x0090639e…243e
0x34b655…2a6f
4 touches
1 conflict
0x1e2019bb…2c3b
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 0x16ba1d5306…8d4480
Audit this contract →
← previous block·next block →recent activity