← previous blocknext block →recent activity
Analyzing
Block #87,667,745
14 transactions · 11 stateful · 2026-07-14 08:53:18 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,667,745 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588c5b6a…60d2
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x1487893e…4055
0x34b655…2a6f
4 touches
1 conflict
0x1a017137…af9f
0x34b655…2a6f
4 touches
1 conflict
0x1a1df941…41d5
0x34b655…2a6f
4 touches
1 conflict
0x1c5d445b…7a6c
0x34b655…2a6f
4 touches
1 conflict
0x2df6f59b…d662
0x34b655…2a6f
4 touches
1 conflict
0x2f14cd2c…b5f4
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 0x588c5b6adb…3060d2
Audit this contract →
← previous block·next block →recent activity