← previous blocknext block →recent activity
Analyzing
Block #89,826,803
42 transactions · 39 stateful · 2026-07-24 04:54:20 UTC
Parallelism
64/100
Blocked
64%
Avg conflicts / tx
4.07
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #89,826,803 · 42 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
12w013w014w115w217w318w419w120w521w622w223w724w825w326w927w1028w429w1130w1232w1333w534w1435w636w737w839w940w1041w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
30 touches
105 conflicts
0x92339d95…0800
0x0000a8…8888
24 touches
66 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x18c62602…91ef
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: 0xb1c8ead4…c38888
105 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity