← previous blocknext block →recent activity
Analyzing
Block #87,051,429
14 transactions · 14 stateful · 2026-07-11 12:11:14 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,051,429 · 14 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
1w02w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ba014e3…35d5
0x34b655…2a6f
6 touches
3 conflicts
0x8d0d8061…d410
0xc8689a…ee79
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe6273ef0…2328
0x34b655…2a6f
4 touches
1 conflict
0xeab8b522…d3e6
0x34b655…2a6f
4 touches
1 conflict
0xf481b267…dc7d
0x34b655…2a6f
4 touches
1 conflict
0xf982b915…898b
0x34b655…2a6f
4 touches
1 conflict
0x21cb17ba…8c94
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 0x3ba014e38a…cf35d5
Audit this contract →
← previous block·next block →recent activity