← previous blocknext block →recent activity
Analyzing
Block #89,545,195
14 transactions · 14 stateful · 2026-07-23 02:10:04 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,545,195 · 14 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
5w06w17w28w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89c4fedf…b215
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x89c4fedf…b214
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xdb89ef9a…606c
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xdf6231bc…5652
0x34b655…2a6f
5 touches
3 conflicts
0x6a6e42c5…9438
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 0x89c4fedfd4…89b215
Audit this contract →
← previous block·next block →recent activity