← previous blocknext block →recent activity
Analyzing
Block #94,841,418
28 transactions · 27 stateful · 2026-08-10 18:01:22 UTC
Parallelism
75/100
Blocked
63%
Avg conflicts / tx
1.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,841,418 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w08w19w110w211w313w214w322w123w125w426w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
10 touches
10 conflicts
0xce1623d9…293b
0x968279…9342
8 touches
6 conflicts
0x30abdd37…9550
0x968279…9342
8 touches
6 conflicts
0x30abdd37…9552
0x968279…9342
8 touches
6 conflicts
0xce1623d9…2934
0x968279…9342
8 touches
6 conflicts
0xce1623d9…2935
0x968279…9342
8 touches
6 conflicts
0xce1623d9…2938
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: Perpl
10 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity