← previous blocknext block →recent activity
Analyzing
Block #87,052,435
16 transactions · 16 stateful · 2026-07-11 12:17:57 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,052,435 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w49w510w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
6 touches
3 conflicts
0x9199a85a…acd9
0x34b655…2a6f
6 touches
3 conflicts
0x0e52d81f…461e
0x34b655…2a6f
4 touches
1 conflict
0x1c03f81f…b303
0x34b655…2a6f
4 touches
1 conflict
0x1c03f81f…b304
0x34b655…2a6f
4 touches
1 conflict
0x1c503794…b0da
0x34b655…2a6f
4 touches
1 conflict
0x453f53a8…e541
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity