← previous blocknext block →recent activity
Analyzing
Block #93,279,766
18 transactions · 15 stateful · 2026-08-05 06:50:20 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.89
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,279,766 · 18 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
2w03w14w26w07w010w111w212w313w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6cafaca…cb5e
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x6499e0b9…9334
0x968279…9342
8 touches
6 conflicts
0x6499e0b9…9335
0x968279…9342
8 touches
6 conflicts
0x6499e0b9…9338
0x968279…9342
8 touches
6 conflicts
0x6499e0b9…9339
0x968279…9342
8 touches
6 conflicts
0x6499e0b9…933b
0x968279…9342
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: 0x96827978…f09342
6 conflicts on slot 0xd6cafaca5a…56cb5e
Audit this contract →
← previous block·next block →recent activity