← previous blocknext block →recent activity
Analyzing
Block #87,286,589
25 transactions · 25 stateful · 2026-07-12 14:23:45 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,286,589 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w18w29w313w114w216w118w019w422w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0004
0xb1dbf0…c0d3
6 touches
3 conflicts
0x7f430e47…4cbd
0xb1dbf0…c0d3
5 touches
3 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
5 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7525206c…fbd5
0x34b655…2a6f
4 touches
1 conflict
0x9ad3be82…b972
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity