← previous blocknext block →recent activity
Analyzing
Block #87,662,261
16 transactions · 11 stateful · 2026-07-14 08:16:39 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,662,261 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x20d1947c…4807
0x34b655…2a6f
4 touches
1 conflict
0x03afadfb…d3a4
0x34b655…2a6f
2 touches
0 conflicts
0x0ef0bd48…a68b
0x34b655…2a6f
2 touches
0 conflicts
0x293fed86…ed95
0x34b655…2a6f
2 touches
0 conflicts
0x3e0072a8…95fc
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity