← previous blocknext block →recent activity
Analyzing
Block #89,865,307
14 transactions · 13 stateful · 2026-07-24 08:08:21 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,865,307 · 14 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
1w05w17w08w29w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a453235…a86f
0x34b655…2a6f
6 touches
3 conflicts
0x989252a1…d812
0xa6afd3…d132
6 touches
3 conflicts
0x6847107a…f468
0xa6afd3…d132
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
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 0x4a45323521…0ba86f
Audit this contract →
← previous block·next block →recent activity