← previous blocknext block →recent activity
Analyzing
Block #87,488,291
23 transactions · 16 stateful · 2026-07-13 12:52:31 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,488,291 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w111w112w213w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x96bfa04d…d06b
0x34b655…2a6f
6 touches
3 conflicts
0xb9266685…8b1d
0x34b655…2a6f
6 touches
3 conflicts
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0x44e13e21…432d
0x34b655…2a6f
4 touches
1 conflict
0x5e2ddc8a…b7a5
0x34b655…2a6f
4 touches
1 conflict
0x63087fbb…5067
0x34b655…2a6f
4 touches
1 conflict
0x909def91…71d2
0x851145…3f07
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