← previous blocknext block →recent activity
Analyzing
Block #94,809,945
40 transactions · 36 stateful · 2026-08-10 15:23:01 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
1.27
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,809,945 · 40 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
2w03w14w27w38w09w111w012w013w114w115w216w217w318w420w121w327w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x808129fc…f97d
0x34b655…2a6f
8 touches
6 conflicts
0x09070832…3996
0x968279…9342
8 touches
6 conflicts
0x09070832…3998
0x968279…9342
8 touches
6 conflicts
0xca8820f5…416c
0x968279…9342
8 touches
6 conflicts
0xca8820f5…416d
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