← previous blocknext block →recent activity
Analyzing
Block #89,596,077
24 transactions · 22 stateful · 2026-07-23 07:49:54 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,596,077 · 24 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
1w04w17w08w19w010w111w013w015w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xcc616f7f…6178
0x34b655…2a6f
6 touches
3 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
4 touches
1 conflict
0x26acd5b4…4f06
0x34b655…2a6f
4 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x4360b49f…140d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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