← previous blocknext block →recent activity
Analyzing
Block #87,792,041
58 transactions · 33 stateful · 2026-07-14 22:45:00 UTC
Parallelism
72/100
Blocked
70%
Avg conflicts / tx
1.57
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,792,041 · 58 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w112w219w023w024w131w132w233w334w435w536w637w738w839w943w1046w248w349w450w557w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x1941b441…5889
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x08636046…e60f
0x34b655…2a6f
10 touches
10 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
8 touches
6 conflicts
0x4ae3b148…7ed2
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x04a566e1…26f3
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity