← previous blocknext block →recent activity
Analyzing
Block #87,317,455
10 transactions · 9 stateful · 2026-07-12 17:50:07 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,317,455 · 10 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
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x8620c47a…99dc
0x34b655…2a6f
4 touches
1 conflict
0xbc94dfe1…0b3d
0x34b655…2a6f
4 touches
1 conflict
0xd7320039…3bc0
0x34b655…2a6f
4 touches
1 conflict
0x7f3ca729…0c7d
0x34b655…2a6f
4 touches
1 conflict
0xf5c132ea…e166
0x34b655…2a6f
4 touches
1 conflict
0xd7320039…3bbf
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity