← previous blocknext block →recent activity
Analyzing
Block #87,578,172
20 transactions · 17 stateful · 2026-07-13 22:54:30 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,578,172 · 20 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
4w07w18w29w313w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x558fd353…1c6b
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x535cbffe…d71e
0x34b655…2a6f
4 touches
1 conflict
0x702cd11f…652b
0x34b655…2a6f
4 touches
1 conflict
0x71cd2af8…dbd4
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
6 conflicts on slot 0x558fd353c6…4b1c6b
Audit this contract →
← previous block·next block →recent activity