← previous blocknext block →recent activity
Analyzing
Block #87,616,812
26 transactions · 19 stateful · 2026-07-14 03:12:55 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,616,812 · 26 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
1w02w112w013w116w217w018w319w220w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x375e887b…a361
0x34b655…2a6f
4 touches
1 conflict
0x49f75237…44f4
0x34b655…2a6f
4 touches
1 conflict
0x689d5e98…d068
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x75b43fdd…8dc1
0x34b655…2a6f
4 touches
1 conflict
0x91d48be7…e4e8
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 0xd93edb3f20…0394ec
Audit this contract →
← previous block·next block →recent activity