← previous blocknext block →recent activity
Analyzing
Block #87,878,748
16 transactions · 15 stateful · 2026-07-15 08:24:56 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,878,748 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w29w311w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xcf5ef070…7d4f
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa2ea76a0…a726
0x34b655…2a6f
6 touches
3 conflicts
0xb59fab73…57e0
0x34b655…2a6f
6 touches
3 conflicts
0x7634a3f4…7f24
0x34b655…2a6f
6 touches
3 conflicts
0x9aea124d…de52
0x34b655…2a6f
4 touches
1 conflict
0xc7981744…932f
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity