← previous blocknext block →recent activity
Analyzing
Block #87,726,799
14 transactions · 11 stateful · 2026-07-14 15:28:34 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,726,799 · 14 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
4w07w08w19w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49f5a697…72c0
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7b6c252d…a696
0x34b655…2a6f
4 touches
1 conflict
0x80fd3987…2314
0x34b655…2a6f
4 touches
1 conflict
0xa0ebadea…4145
0x34b655…2a6f
4 touches
1 conflict
0xf8c9546a…ebba
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
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
10 conflicts on slot 0x49f5a69781…bc72c0
Audit this contract →
← previous block·next block →recent activity