← previous blocknext block →recent activity
Analyzing
Block #89,595,314
12 transactions · 12 stateful · 2026-07-23 07:44:48 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,595,314 · 12 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
1w02w13w28w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac111fea…4e4f
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1d68c976…b6e6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x132737f4…b284
0x0594c7…a3be
2 touches
0 conflicts
0xbb05cfd1…bce9
0x0594c7…a3be
2 touches
0 conflicts
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 0xac111feaa1…884e4f
Audit this contract →
← previous block·next block →recent activity