← previous blocknext block →recent activity
Analyzing
Block #87,621,475
18 transactions · 17 stateful · 2026-07-14 03:44:04 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,621,475 · 18 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
3w04w05w16w29w310w215w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cd78950…607c
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xf9516d52…5364
0x34b655…2a6f
6 touches
3 conflicts
0xc9fe0433…7f01
0x34b655…2a6f
6 touches
3 conflicts
0xd026fe03…7748
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
6 touches
3 conflicts
0xe7a04bd8…289b
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 0x7cd7895083…92607c
Audit this contract →
← previous block·next block →recent activity