← previous blocknext block →recent activity
Analyzing
Block #89,827,008
43 transactions · 40 stateful · 2026-07-24 04:55:22 UTC
Parallelism
67/100
Blocked
73%
Avg conflicts / tx
4.33
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #89,827,008 · 43 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w114w015w016w117w118w219w320w221w422w523w324w625w726w427w828w530w632w736w838w939w1040w1141w1242w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
28 touches
91 conflicts
0x92339d95…0800
0x0000a8…8888
28 touches
91 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
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: 0xb1c8ead4…c38888
91 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity