← previous blocknext block →recent activity
Analyzing
Block #89,751,648
31 transactions · 30 stateful · 2026-07-23 22:35:03 UTC
Parallelism
58/100
Blocked
67%
Avg conflicts / tx
3.1
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #89,751,648 · 31 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w18w313w014w015w116w117w218w219w320w321w422w423w524w625w726w827w928w1029w1130w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
26 touches
78 conflicts
0x92339d95…0800
0xb1c8ea…8888
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
8 touches
6 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
6 touches
3 conflicts
0x4df77c4f…0e85
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
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
78 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity