← previous blocknext block →recent activity
Analyzing
Block #87,758,929
23 transactions · 22 stateful · 2026-07-14 19:03:28 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,758,929 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w315w316w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fb86cd0…c67c
0x34b655…2a6f
8 touches
6 conflicts
0x1c03f81f…b304
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xd50d8366…df9d
0x34b655…2a6f
6 touches
3 conflicts
0x453f53a8…e541
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x6d156df4…b644
0x34b655…2a6f
4 touches
1 conflict
0x03c2acba…6f0f
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 0x4fb86cd027…a5c67c
Audit this contract →
← previous block·next block →recent activity