← previous blocknext block →recent activity
Analyzing
Block #94,953,375
23 transactions · 20 stateful · 2026-08-11 03:24:28 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,953,375 · 23 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
1w03w15w26w08w39w110w011w112w113w214w315w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c98f2fe…e3b4
0x968279…9342
8 touches
6 conflicts
0x6bab8831…4339
0x968279…9342
8 touches
6 conflicts
0x6bab8831…4337
0x968279…9342
8 touches
6 conflicts
0x6bab8831…4336
0x968279…9342
8 touches
6 conflicts
0x1c98f2fe…e3b9
0x968279…9342
8 touches
6 conflicts
0x1c98f2fe…e3b8
0x968279…9342
8 touches
6 conflicts
0x1c98f2fe…e3b7
0x968279…9342
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
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 0x1c98f2fe3b…11e3b4
Audit this contract →
← previous block·next block →recent activity