← previous blocknext block →recent activity
Analyzing
Block #87,063,336
16 transactions · 13 stateful · 2026-07-11 13:30:46 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,063,336 · 16 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
1w02w13w07w08w19w110w211w214w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b2b1640…1bb8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x220a8541…6431
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x4e009112…6ef3
0x34b655…2a6f
4 touches
1 conflict
0x4e66a473…9fe8
0x34b655…2a6f
4 touches
1 conflict
0x51a9fa57…1dff
0x34b655…2a6f
4 touches
1 conflict
0x56b5f5c0…a3ad
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 0x4b2b1640a8…3c1bb8
Audit this contract →
← previous block·next block →recent activity