← previous blocknext block →recent activity
Analyzing
Block #89,525,775
18 transactions · 18 stateful · 2026-07-23 00:00:27 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,525,775 · 18 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
5w08w110w211w012w113w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdb90664a…76c7
0x0a2fbf…29b1
4 touches
1 conflict
0xdb90664a…76ca
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x57b3b97e…7ca7
0x34b655…2a6f
4 touches
1 conflict
0x785e0532…1473
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xa08f40b255…099a93
Audit this contract →
← previous block·next block →recent activity