← previous blocknext block →recent activity
Analyzing
Block #94,742,620
20 transactions · 19 stateful · 2026-08-10 09:43:34 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,742,620 · 20 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
1w02w03w14w25w36w48w59w610w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59d087de…253e
0x968279…9342
12 touches
15 conflicts
0x00000000…0006
0x968279…9342
12 touches
15 conflicts
0x136e846d…4ccb
0x968279…9342
12 touches
15 conflicts
0x136e846d…4ccc
0x968279…9342
12 touches
15 conflicts
0x136e846d…4cce
0x968279…9342
12 touches
15 conflicts
0x59d087de…2537
0x968279…9342
12 touches
15 conflicts
0x59d087de…2538
0x968279…9342
12 touches
15 conflicts
0x59d087de…253b
0x968279…9342
12 touches
15 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: 0x96827978…f09342
15 conflicts on slot 0x59d087decb…f6253e
Audit this contract →
← previous block·next block →recent activity