← previous blocknext block →recent activity
Analyzing
Block #89,596,860
21 transactions · 20 stateful · 2026-07-23 07:55:08 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,596,860 · 21 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
3w04w15w28w09w111w312w013w114w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x06d44196…338d
0x0a2fbf…29b1
4 touches
1 conflict
0x06d44196…3390
0x0a2fbf…29b1
4 touches
1 conflict
0x06d44196…3392
0x0a2fbf…29b1
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x164ef99f…63ad
0x34b655…2a6f
4 touches
1 conflict
0x403a02ac…b163
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity