← previous blocknext block →recent activity
Analyzing
Block #93,922,339
19 transactions · 17 stateful · 2026-08-07 12:41:14 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,922,339 · 19 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
1w02w13w04w26w39w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6b90520…f384
0xe52b14…7230
12 touches
15 conflicts
0x9c70dec2…1719
0xe52b14…7230
12 touches
15 conflicts
0x77550e63…2cbe
0xe52b14…7230
12 touches
15 conflicts
0x77550e63…2cc0
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 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 0xe6b9052034…27f384
Audit this contract →
← previous block·next block →recent activity