← previous blocknext block →recent activity
Analyzing
Block #89,752,281
22 transactions · 19 stateful · 2026-07-23 22:38:14 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,752,281 · 22 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
1w02w13w24w06w18w09w110w211w314w016w017w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6a9f
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6aa0
0x2b46c0…1669
4 touches
1 conflict
0xea8e47b0…abfe
0x2b46c0…1669
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity