← previous blocknext block →recent activity
Analyzing
Block #89,740,336
10 transactions · 10 stateful · 2026-07-23 21:37:52 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,740,336 · 10 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
2w03w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xb37dfb6b…268f
0x34b655…2a6f
4 touches
1 conflict
0xc6b604e6…5152
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xcadb6fae…b614
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 0xd6d040d989…9c9ae3
Audit this contract →
← previous block·next block →recent activity