← previous blocknext block →recent activity
Analyzing
Block #87,661,912
36 transactions · 28 stateful · 2026-07-14 08:14:19 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,661,912 · 36 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
2w03w15w06w17w08w112w213w317w119w222w327w128w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x944bfd2a…49f7
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6b366ba5…81ec
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0x944bfd2a9b…5b49f7
Audit this contract →
← previous block·next block →recent activity