← previous blocknext block →recent activity
Analyzing
Block #87,713,605
21 transactions · 19 stateful · 2026-07-14 14:00:09 UTC
Parallelism
71/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,713,605 · 21 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
1w02w15w16w011w212w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e5239e9…ee6e
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x6efac147…d278
0x34b655…2a6f
4 touches
1 conflict
0x722851f4…73fe
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9f3dd8dc…802a
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
1 conflict on slot 0x2e5239e91a…19ee6e
Audit this contract →
← previous block·next block →recent activity