← previous blocknext block →recent activity
Analyzing
Block #93,359,659
50 transactions · 38 stateful · 2026-08-05 13:32:01 UTC
Parallelism
86/100
Blocked
58%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,359,659 · 50 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w311w413w515w642w243w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc1985f97…d7ea
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c5
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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: 0x91855e79…58ac7e
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity