← previous blocknext block →recent activity
Analyzing
Block #94,999,087
11 transactions · 9 stateful · 2026-08-11 07:14:22 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,999,087 · 11 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
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d9d448e…a04c
0x968279…9342
8 touches
6 conflicts
0x3d9d448e…a04f
0x968279…9342
8 touches
6 conflicts
0x3d9d448e…a050
0x968279…9342
8 touches
6 conflicts
0x3d9d448e…a052
0x968279…9342
8 touches
6 conflicts
0xb86e1978…ac1a
0x968279…9342
8 touches
6 conflicts
0xb86e1978…ac1b
0x968279…9342
8 touches
6 conflicts
0xb86e1978…ac1d
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 0x3d9d448e0c…e9a04c
Audit this contract →
← previous block·next block →recent activity