← previous blocknext block →recent activity
Analyzing
Block #89,673,487
14 transactions · 14 stateful · 2026-07-23 16:00:17 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,673,487 · 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
1w02w03w14w15w06w07w18w29w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0036
0x39f901…6bdf
4 touches
1 conflict
0xc5819118…1448
0x39f901…6bdf
4 touches
1 conflict
0x00000000…0004
0x4e8aae…4298
4 touches
1 conflict
0xbb371eab…3efc
0x4e8aae…4298
4 touches
1 conflict
0x63d273cc…f2ec
0x80f006…d585
4 touches
1 conflict
0x63d273cc…f2ed
0x80f006…d585
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity