← previous blocknext block →recent activity
Analyzing
Block #94,809,929
26 transactions · 25 stateful · 2026-08-10 15:22:56 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #94,809,929 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w519w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
16 touches
28 conflicts
0xca8820f5…416f
0x968279…9342
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x09070832…3991
0x968279…9342
8 touches
6 conflicts
0x09070832…3992
0x968279…9342
8 touches
6 conflicts
0x09070832…3995
0x968279…9342
8 touches
6 conflicts
0x09070832…3996
0x968279…9342
8 touches
6 conflicts
0x09070832…3998
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
28 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity