← previous blocknext block →recent activity
Analyzing
Block #89,742,589
48 transactions · 45 stateful · 2026-07-23 21:49:17 UTC
Parallelism
65/100
Blocked
71%
Avg conflicts / tx
4.4
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #89,742,589 · 48 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w110w211w312w417w018w119w020w021w122w123w224w225w326w327w428w429w530w533w636w739w842w944w1046w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
34 touches
136 conflicts
0x92339d95…0800
0x0000a8…8888
24 touches
66 conflicts
0xbb322930…ace5
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x9e5adfc8…489d
0x34b655…2a6f
6 touches
3 conflicts
0xb180b657…e7dc
0x34b655…2a6f
6 touches
3 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
136 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity