← previous blocknext block →recent activity
Analyzing
Block #87,734,794
13 transactions · 11 stateful · 2026-07-14 16:22:02 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,734,794 · 13 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
1w05w06w17w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf5ef070…7d4f
0x34b655…2a6f
8 touches
6 conflicts
0x8eed7e30…c1ef
0x34b655…2a6f
6 touches
3 conflicts
0x5b549c4c…53a6
0x40c49f…2af0
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x24e3bf88…17bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc6bb7e6c…bf35
0x34b655…2a6f
4 touches
1 conflict
0xf2e22c06…42d6
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 0xcf5ef07060…d87d4f
Audit this contract →
← previous block·next block →recent activity