← previous blocknext block →recent activity
Analyzing
Block #89,579,411
18 transactions · 16 stateful · 2026-07-23 05:58:37 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,579,411 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w09w110w011w112w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbc0c65c4…7ece
0x0a2fbf…29b1
4 touches
1 conflict
0xeac0c96e…b7fb
0x0a2fbf…29b1
4 touches
1 conflict
0xeac0c96e…b7fc
0x0a2fbf…29b1
4 touches
1 conflict
0xeac0c96e…b7ff
0x0a2fbf…29b1
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity