← previous blocknext block →recent activity
Analyzing
Block #87,664,516
17 transactions · 14 stateful · 2026-07-14 08:31:44 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,664,516 · 17 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
1w02w13w04w110w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f2f3106…6b83
0x34b655…2a6f
4 touches
1 conflict
0xec44d077…2dff
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…154a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…153c
0x34b655…2a6f
4 touches
1 conflict
0xbe44dcb9…94c2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x74500de0…8b2c
0x34b655…2a6f
4 touches
1 conflict
0x71604178…a3a8
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 0x1f2f31063d…6a6b83
Audit this contract →
← previous block·next block →recent activity