← previous blocknext block →recent activity
Analyzing
Block #89,737,748
9 transactions · 9 stateful · 2026-07-23 21:24:47 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,737,748 · 9 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
2w03w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc204ea3…f1a3
0x34b655…2a6f
6 touches
3 conflicts
0xf607560e…828a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x85d21fba…c8b2
0x34b655…2a6f
4 touches
1 conflict
0xadea0cd8…1d83
0x34b655…2a6f
4 touches
1 conflict
0xb6c52a60…0076
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xdc204ea323…a5f1a3
Audit this contract →
← previous block·next block →recent activity