← previous blocknext block →recent activity
Analyzing
Block #87,689,791
24 transactions · 21 stateful · 2026-07-14 11:20:39 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,689,791 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w08w19w210w313w414w515w017w118w519w520w123w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x0bf6328c…2bd4
0x34b655…2a6f
4 touches
1 conflict
0x0efa614d…4d73
0x34b655…2a6f
4 touches
1 conflict
0x0f068b13…fb19
0x34b655…2a6f
4 touches
1 conflict
0x156b161b…ef04
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity