← previous blocknext block →recent activity
Analyzing
Block #89,708,300
38 transactions · 38 stateful · 2026-07-23 18:56:06 UTC
Parallelism
58/100
Blocked
76%
Avg conflicts / tx
4.55
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #89,708,300 · 38 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w38w09w112w013w014w115w116w217w219w320w423w526w628w730w831w932w1033w1134w1235w1336w1437w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
32 touches
120 conflicts
0x92339d95…0800
0xb1c8ea…8888
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x35bd6a25…9de5
0x34b655…2a6f
4 touches
1 conflict
0x3ca268be…8865
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
120 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity