← previous blocknext block →recent activity
Analyzing
Block #89,576,937
9 transactions · 7 stateful · 2026-07-23 05:42:07 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,576,937 · 9 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33175a5b…a435
0x34b655…2a6f
4 touches
1 conflict
0x5f2c121e…8f3c
0x34b655…2a6f
4 touches
1 conflict
0x5f2c121e…8f3d
0x34b655…2a6f
4 touches
1 conflict
0x4ebf04a8…42e6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf346808d…6ad4
0x34b655…2a6f
4 touches
1 conflict
0xb308a160…aba3
0x34b655…2a6f
3 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
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 0x33175a5b11…7aa435
Audit this contract →
← previous block·next block →recent activity