← previous blocknext block →recent activity
Analyzing
Block #94,816,564
50 transactions · 44 stateful · 2026-08-10 15:56:19 UTC
Parallelism
70/100
Blocked
73%
Avg conflicts / tx
2
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #94,816,564 · 50 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w09w111w212w013w114w215w016w117w118w219w220w321w329w731w936w739w340w441w1042w845w1147w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x160f117d…8e90
0x065c9d…c394
8 touches
6 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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
15 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity