← previous blocknext block →recent activity
Analyzing
Block #89,770,679
12 transactions · 10 stateful · 2026-07-24 00:11:07 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,770,679 · 12 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
2w03w16w27w310w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22c6ecc6…c70d
0x34b655…2a6f
4 touches
1 conflict
0x52bca89b…97d8
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa4c56761…79e0
0x34b655…2a6f
4 touches
1 conflict
0xbce969bb…8007
0x34b655…2a6f
4 touches
1 conflict
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
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
1 conflict on slot 0x22c6ecc6f5…a4c70d
Audit this contract →
← previous block·next block →recent activity