← previous blocknext block →recent activity
Analyzing
Block #94,791,951
43 transactions · 39 stateful · 2026-08-10 13:52:30 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
1.95
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #94,791,951 · 43 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w08w19w210w311w012w013w114w115w216w317w425w126w629w231w132w833w234w336w940w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
14 touches
21 conflicts
0x2840c278…bbc7
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xeae24c…0be0
8 touches
6 conflicts
0x160f117d…8e90
0x065c9d…c394
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
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
21 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity