← previous blocknext block →recent activity
Analyzing
Block #87,049,096
14 transactions · 13 stateful · 2026-07-11 11:55:43 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,049,096 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w08w19w210w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c623175…29e4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa248a5dd…4a69
0x34b655…2a6f
6 touches
3 conflicts
0x2a2b68e0…4f55
0x34b655…2a6f
4 touches
1 conflict
0x2ae834f7…a036
0x34b655…2a6f
4 touches
1 conflict
0x2bdda96c…2154
0x34b655…2a6f
4 touches
1 conflict
0x2d66bc61…b923
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
3 conflicts on slot 0x4c62317513…a629e4
Audit this contract →
← previous block·next block →recent activity