← previous blocknext block →recent activity
Analyzing
Block #94,848,779
52 transactions · 47 stateful · 2026-08-10 18:38:24 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
2.58
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #94,848,779 · 52 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w19w010w111w012w213w114w316w418w619w720w821w935w1036w238w339w440w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
12 touches
15 conflicts
0xa558e115…fc88
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xeae24c…0be0
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
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
36 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity