← previous blocknext block →recent activity
Analyzing
Block #87,662,023
14 transactions · 13 stateful · 2026-07-14 08:15:04 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,662,023 · 14 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
2w05w16w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x02f0ef4a…7144
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x35c57efc…6288
0x34b655…2a6f
4 touches
1 conflict
0x386864d1…2778
0x34b655…2a6f
4 touches
1 conflict
0x48a10103…33b1
0x34b655…2a6f
4 touches
1 conflict
0x4997bf76…8a4f
0x34b655…2a6f
4 touches
1 conflict
0x799ee783…1f74
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity