← previous blocknext block →recent activity
Analyzing
Block #89,703,799
18 transactions · 12 stateful · 2026-07-23 18:33:23 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,703,799 · 18 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
4w05w19w014w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7537
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7538
0x34b655…2a6f
4 touches
1 conflict
0x106df0dc…957b
0x34b655…2a6f
4 touches
1 conflict
0x333d8750…01d0
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 0xe06bbb2ef5…889417
Audit this contract →
← previous block·next block →recent activity