← previous blocknext block →recent activity
Analyzing
Block #89,749,793
7 transactions · 6 stateful · 2026-07-23 22:25:41 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,749,793 · 7 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
3w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x046e4d12…847a
0x34b655…2a6f
2 touches
0 conflicts
0x106c514d…bd94
0x34b655…2a6f
2 touches
0 conflicts
0x130d54cc…e587
0x34b655…2a6f
2 touches
0 conflicts
0x19afd281…9cc6
0x34b655…2a6f
2 touches
0 conflicts
0x1da820ae…c04a
0x34b655…2a6f
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 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity