← previous blocknext block →recent activity
Analyzing
Block #94,851,732
30 transactions · 26 stateful · 2026-08-10 18:53:16 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,851,732 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w08w19w010w111w212w215w016w218w319w420w523w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0x2bad40ae…0522
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x1dfd8389…170d
0x34b655…2a6f
6 touches
3 conflicts
0x65487580…b5eb
0x34b655…2a6f
6 touches
3 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
6 touches
3 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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity