← previous blocknext block →recent activity
Analyzing
Block #89,575,183
14 transactions · 11 stateful · 2026-07-23 05:30:25 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,575,183 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc356fce2…51b4
0x34b655…2a6f
4 touches
1 conflict
0xdc836522…677f
0x34b655…2a6f
4 touches
1 conflict
0x21e273cb…b384
0x34b655…2a6f
4 touches
1 conflict
0xeb20d273…7e94
0x34b655…2a6f
4 touches
1 conflict
0xeee60778…2df8
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc5f
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x440a6d0a…3605
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 0xc356fce2ee…8d51b4
Audit this contract →
← previous block·next block →recent activity