← previous blocknext block →recent activity
Analyzing
Block #89,747,350
35 transactions · 30 stateful · 2026-07-23 22:13:19 UTC
Parallelism
60/100
Blocked
73%
Avg conflicts / tx
3.66
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #89,747,350 · 35 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
2w03w111w012w013w114w115w216w217w318w319w420w421w522w523w624w625w726w727w828w829w930w1031w1132w1233w13
- 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
18 touches
36 conflicts
0x1e56edff…5f5b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x046740ca…4066
0x34b655…2a6f
2 touches
0 conflicts
0x2bad40ae…0522
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2266
0x34b655…2a6f
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: 0x0000a8fd…758888
91 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity