← previous blocknext block →recent activity
Analyzing
Block #89,538,197
14 transactions · 13 stateful · 2026-07-23 01:23:16 UTC
Parallelism
57/100
Blocked
62%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,538,197 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w49w510w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x02f10e14…784c
0x34b655…2a6f
4 touches
1 conflict
0x0e43503b…ad4a
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x1aa99bc5…cb98
0x34b655…2a6f
4 touches
1 conflict
0x1cf6a77a…3e12
0x34b655…2a6f
4 touches
1 conflict
0x2fe57c3f…8f29
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity