← previous blocknext block →recent activity
Analyzing
Block #93,922,345
25 transactions · 23 stateful · 2026-08-07 12:41:16 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,922,345 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w18w29w310w411w512w114w216w222w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
10 touches
10 conflicts
0x77550e63…2cc0
0xe52b14…7230
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9c70dec2…1719
0xe52b14…7230
6 touches
3 conflicts
0x8ffa3328…ce11
0xe52b14…7230
6 touches
3 conflicts
0x77550e63…2cbe
0xe52b14…7230
6 touches
3 conflicts
0xe6b90520…f384
0xe52b14…7230
5 touches
3 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: 0xe52b1424…bb7230
15 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity