← previous blocknext block →recent activity
Analyzing
Block #94,812,661
19 transactions · 18 stateful · 2026-08-10 15:36:42 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,812,661 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w28w09w110w211w313w114w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x772ab420…c2f6
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe81f8eb4…e4d1
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x35ee00bd…f240
0xd32edf…ff58
5 touches
3 conflicts
0x810a3aa2…0227
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: Perpl
6 conflicts on slot 0x772ab420dc…dcc2f6
Audit this contract →
← previous block·next block →recent activity