← previous blocknext block →recent activity
Analyzing
Block #87,705,178
21 transactions · 18 stateful · 2026-07-14 13:03:45 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,705,178 · 21 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
1w03w14w09w010w111w215w016w118w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5031114…58ac
0x34b655…2a6f
8 touches
6 conflicts
0x767799cd…f423
0xc8689a…ee79
6 touches
3 conflicts
0x2754c3f9…9863
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xa57576bb…e01f
0x34b655…2a6f
6 touches
3 conflicts
0xad09dd03…27d0
0x34b655…2a6f
6 touches
3 conflicts
0xce40a269…92eb
0x34b655…2a6f
6 touches
3 conflicts
0xe7ceda84…1a3e
0x34b655…2a6f
6 touches
3 conflicts
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 0xc503111436…e358ac
Audit this contract →
← previous block·next block →recent activity