← previous blocknext block →recent activity
Analyzing
Block #89,758,723
7 transactions · 6 stateful · 2026-07-23 23:10:43 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,758,723 · 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
2w04w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bbd28c…e227
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x315e07b8…9823
0x34b655…2a6f
2 touches
0 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
2 touches
0 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
2 touches
0 conflicts
0x47e87014…3b55
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 0x00bbd28c94…39e227
Audit this contract →
← previous block·next block →recent activity