← previous blocknext block →recent activity
Analyzing
Block #87,753,261
12 transactions · 11 stateful · 2026-07-14 18:25:35 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,753,261 · 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
2w03w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5651694…0a1c
0x34b655…2a6f
6 touches
3 conflicts
0x333c820d…10c1
0x34b655…2a6f
6 touches
3 conflicts
0x33da0dfa…bac6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa0b17484…2b19
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xd34b5587…cc86
0x34b655…2a6f
4 touches
1 conflict
0x337f8029…d9cc
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 0xf56516948c…200a1c
Audit this contract →
← previous block·next block →recent activity