← previous blocknext block →recent activity
Analyzing
Block #87,785,366
16 transactions · 13 stateful · 2026-07-14 22:00:22 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,785,366 · 16 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
1w02w03w14w25w36w010w111w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xdfc01d93…9d93
0x34b655…2a6f
6 touches
3 conflicts
0x3e644b16…807b
0x34b655…2a6f
6 touches
3 conflicts
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 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity