← previous blocknext block →recent activity
Analyzing
Block #87,738,567
16 transactions · 14 stateful · 2026-07-14 16:47:17 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,738,567 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w16w07w18w210w311w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x313d3d93…4aa2
0x34b655…2a6f
6 touches
3 conflicts
0x98212952…9ba6
0x34b655…2a6f
6 touches
3 conflicts
0x671703d0…94b1
0x34b655…2a6f
6 touches
3 conflicts
0xbe23d5d8…cddd
0x34b655…2a6f
6 touches
3 conflicts
0xeb9b6ffc…3aab
0x34b655…2a6f
6 touches
3 conflicts
0xeb9b6ffc…3aac
0x34b655…2a6f
6 touches
3 conflicts
0xc9d2172c…fa75
0x34b655…2a6f
5 touches
3 conflicts
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity