← previous blocknext block →recent activity
Analyzing
Block #87,787,781
13 transactions · 13 stateful · 2026-07-14 22:16:31 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,787,781 · 13 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
1w02w15w06w27w38w410w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a81321…6170
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8b37f931…1b3f
0x34b655…2a6f
6 touches
3 conflicts
0x09cd9841…d332
0x34b655…2a6f
4 touches
1 conflict
0x0b826166…904e
0x34b655…2a6f
4 touches
1 conflict
0x0ccb39ed…3680
0x34b655…2a6f
4 touches
1 conflict
0x14d006f0…9c4e
0x34b655…2a6f
4 touches
1 conflict
0x159aac52…c583
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 0x05a81321f8…ba6170
Audit this contract →
← previous block·next block →recent activity