← previous blocknext block →recent activity
Analyzing
Block #87,611,414
16 transactions · 13 stateful · 2026-07-14 02:36:48 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,611,414 · 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
2w04w05w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe63cb2d0…c66f
0x34b655…2a6f
4 touches
1 conflict
0x212c5b04…5f01
0x34b655…2a6f
4 touches
1 conflict
0x6fca8941…b68b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x98afad44…850d
0x34b655…2a6f
4 touches
1 conflict
0x98afad44…850e
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xcdf6703d…9c79
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
1 conflict on slot 0xe63cb2d004…37c66f
Audit this contract →
← previous block·next block →recent activity