← previous blocknext block →recent activity
Analyzing
Block #87,725,038
10 transactions · 9 stateful · 2026-07-14 15:16:46 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,725,038 · 10 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
1w03w04w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f35c56f…046b
0x34b655…2a6f
4 touches
1 conflict
0x68761f35…6026
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
2 touches
0 conflicts
0x1172247d…0022
0x34b655…2a6f
2 touches
0 conflicts
0x1191dbf7…8e85
0x34b655…2a6f
2 touches
0 conflicts
0x11dd03cd…4e54
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x2f35c56f7b…bd046b
Audit this contract →
← previous block·next block →recent activity