← previous blocknext block →recent activity
Analyzing
Block #89,740,927
14 transactions · 14 stateful · 2026-07-23 21:40:51 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,740,927 · 14 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
3w05w16w07w29w312w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda6ebfcf…d51e
0x34b655…2a6f
4 touches
1 conflict
0xe1caddba…a708
0x34b655…2a6f
4 touches
1 conflict
0x00075ae5…3a98
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2a6ce996…6902
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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 0xe21234e760…98bded
Audit this contract →
← previous block·next block →recent activity