← previous blocknext block →recent activity
Analyzing
Block #89,881,584
22 transactions · 20 stateful · 2026-07-24 09:30:14 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,881,584 · 22 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
1w02w13w28w09w310w111w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b5b2ce…c5bb
0xfa32f9…f3f0
8 touches
6 conflicts
0x99f666e3…b2a2
0x3bd359…433a
8 touches
6 conflicts
0x9194f4a3…10b8
0x754704…b603
8 touches
6 conflicts
0x00000000…0000
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0001
0xfa32f9…f3f0
8 touches
6 conflicts
0x41c66186…229a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe3684e08…c96a
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: 0xfa32f9ec…fef3f0
6 conflicts on slot 0x38b5b2ceac…4cc5bb
Audit this contract →
← previous block·next block →recent activity