← previous blocknext block →recent activity
Analyzing
Block #87,713,204
16 transactions · 13 stateful · 2026-07-14 13:57:28 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,713,204 · 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
2w03w18w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xf4f4af3b…c5bd
0x34b655…2a6f
4 touches
1 conflict
0xc893169b…6d75
0x34b655…2a6f
4 touches
1 conflict
0xc8d31c56…91df
0x34b655…2a6f
4 touches
1 conflict
0xee06e767…00d6
0x34b655…2a6f
4 touches
1 conflict
0x02f0ef4a…7144
0x34b655…2a6f
4 touches
1 conflict
0x293fed86…ed95
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity