← previous blocknext block →recent activity
Analyzing
Block #89,597,254
16 transactions · 15 stateful · 2026-07-23 07:57:46 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,597,254 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w19w010w112w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7d3e24a…0eb8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xee198dae…2dbb
0x34b655…2a6f
4 touches
1 conflict
0xc516fef7…841c
0x34b655…2a6f
4 touches
1 conflict
0x496ff651…1310
0x34b655…2a6f
4 touches
1 conflict
0xf68f475d…ced3
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
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
3 conflicts on slot 0xa7d3e24aa2…eb0eb8
Audit this contract →
← previous block·next block →recent activity