← previous blocknext block →recent activity
Analyzing
Block #87,750,050
19 transactions · 19 stateful · 2026-07-14 18:04:07 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,750,050 · 19 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
1w02w13w210w011w112w214w217w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xa84ac543…8b65
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xdf15e2bf…d7a9
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2879
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa209b7b4…206c
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 0x0dd44476b8…7fef40
Audit this contract →
← previous block·next block →recent activity