← previous blocknext block →recent activity
Analyzing
Block #94,852,558
15 transactions · 15 stateful · 2026-08-10 18:57:25 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,852,558 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w49w510w611w712w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee085853…1a8b
0x968279…9342
16 touches
28 conflicts
0xee085853…1a8c
0x968279…9342
16 touches
28 conflicts
0xee085853…1a8f
0x968279…9342
16 touches
28 conflicts
0xee085853…1a90
0x968279…9342
16 touches
28 conflicts
0xee085853…1a91
0x968279…9342
16 touches
28 conflicts
0xe0ef18f0…83f5
0x968279…9342
16 touches
28 conflicts
0xe0ef18f0…83f7
0x968279…9342
16 touches
28 conflicts
0x177211e2…1c2d
0x754704…b603
16 touches
28 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
28 conflicts on slot 0xee085853c0…4b1a8b
Audit this contract →
← previous block·next block →recent activity