← previous blocknext block →recent activity
Analyzing
Block #87,735,574
20 transactions · 19 stateful · 2026-07-14 16:27:15 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,735,574 · 20 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
1w02w14w07w08w19w213w114w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x07c4edd2…3022
0x34b655…2a6f
4 touches
1 conflict
0x22e7ebfe…1293
0x34b655…2a6f
4 touches
1 conflict
0x26050074…6967
0x34b655…2a6f
4 touches
1 conflict
0x33d69c2d…1021
0x34b655…2a6f
4 touches
1 conflict
0x38ad639c…6a18
0x34b655…2a6f
4 touches
1 conflict
0x38ad639c…6a19
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 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity