← previous blocknext block →recent activity
Analyzing
Block #89,828,244
43 transactions · 38 stateful · 2026-07-24 05:01:37 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
3.74
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #89,828,244 · 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
1w02w16w07w18w215w016w017w118w220w321w423w524w625w126w727w828w229w930w1031w332w1133w434w535w636w737w838w939w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
28 touches
91 conflicts
0x92339d95…0800
0xb1c8ea…8888
24 touches
66 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x921a58d1…db22
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: 0x0000a8fd…758888
91 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity