← previous blocknext block →recent activity
Analyzing
Block #87,588,662
43 transactions · 27 stateful · 2026-07-14 00:04:39 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,588,662 · 43 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
2w013w116w019w223w124w226w028w131w241w342w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64687417…8d60
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x169daa40…3f75
0x34b655…2a6f
4 touches
1 conflict
0x2aebf983…10d7
0x34b655…2a6f
4 touches
1 conflict
0x36187d32…57e2
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
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 0x64687417b8…b08d60
Audit this contract →
← previous block·next block →recent activity