← previous blocknext block →recent activity
Analyzing
Block #89,750,617
10 transactions · 8 stateful · 2026-07-23 22:29:49 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,750,617 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502b445c…c1e5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x1bd6ddeb…9a19
0x34b655…2a6f
2 touches
0 conflicts
0x2647f76f…6ca1
0x34b655…2a6f
2 touches
0 conflicts
0x27775de2…d5cc
0x34b655…2a6f
2 touches
0 conflicts
0x281fe64f…dd42
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x502b445c24…f1c1e5
Audit this contract →
← previous block·next block →recent activity