← previous blocknext block →recent activity
Analyzing
Block #89,749,737
36 transactions · 33 stateful · 2026-07-23 22:25:23 UTC
Parallelism
64/100
Blocked
64%
Avg conflicts / tx
2.56
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #89,749,737 · 36 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
1w02w13w27w08w19w010w213w215w016w318w019w120w021w022w123w124w225w226w327w428w529w630w731w832w933w1034w1135w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
26 touches
78 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x92339d95…0800
0xb1c8ea…8888
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc64c7dc8…8c62
0x34b655…2a6f
4 touches
1 conflict
0xc64c7dc8…8c63
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