← previous blocknext block →recent activity
Analyzing
Block #87,785,839
21 transactions · 19 stateful · 2026-07-14 22:03:32 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,785,839 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w28w312w313w415w116w217w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb431eafe…2fc8
0x34b655…2a6f
8 touches
6 conflicts
0xc08384da…ecb7
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x3a51d8ed…0c97
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49c468db…0b1a
0x34b655…2a6f
4 touches
1 conflict
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
6 conflicts on slot 0xb431eafe6f…a92fc8
Audit this contract →
← previous block·next block →recent activity