← previous blocknext block →recent activity
Analyzing
Block #89,376,982
16 transactions · 13 stateful · 2026-07-22 07:26:05 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,376,982 · 16 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
1w03w04w15w29w310w414w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7213efec…c753
0x34b655…2a6f
8 touches
6 conflicts
0xba059816…a847
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x7a9059f1…de42
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 0x7213efec42…ddc753
Audit this contract →
← previous block·next block →recent activity