← previous blocknext block →recent activity
Analyzing
Block #89,881,603
25 transactions · 23 stateful · 2026-07-24 09:30:19 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,881,603 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w28w29w010w111w213w014w117w218w320w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c66186…229a
0x34b655…2a6f
6 touches
3 conflicts
0x905a2dd7…1dfc
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x2b9c6652…d14e
0x754704…b603
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
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 0x41c661864c…30229a
Audit this contract →
← previous block·next block →recent activity