← previous blocknext block →recent activity
Analyzing
Block #87,786,027
20 transactions · 17 stateful · 2026-07-14 22:04:48 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,786,027 · 20 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
1w02w14w05w112w213w314w415w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb91a6f59…722c
0x34b655…2a6f
6 touches
3 conflicts
0x05a81321…6170
0x34b655…2a6f
6 touches
3 conflicts
0x3a51d8ed…0c97
0x34b655…2a6f
4 touches
1 conflict
0x3e644b16…807b
0x34b655…2a6f
4 touches
1 conflict
0x46ccdabb…16fc
0x34b655…2a6f
4 touches
1 conflict
0x4a27d622…e4ac
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity