← previous blocknext block →recent activity
Analyzing
Block #89,681,360
19 transactions · 18 stateful · 2026-07-23 16:40:15 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,681,360 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w08w111w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x53cccb07…d7f0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00950c90…3351
0x0a2fbf…29b1
4 touches
1 conflict
0xe273b3b9…4d69
0x0a2fbf…29b1
4 touches
1 conflict
0xe273b3b9…4d6a
0x0a2fbf…29b1
4 touches
1 conflict
0x0c7159f3…4391
0x34b655…2a6f
4 touches
1 conflict
0x27754bd4…96ae
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity