← previous blocknext block →recent activity
Analyzing
Block #94,791,588
34 transactions · 29 stateful · 2026-08-10 13:50:40 UTC
Parallelism
85/100
Blocked
59%
Avg conflicts / tx
1.12
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,791,588 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w09w110w211w212w313w420w324w328w229w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xf6fc032b…d173
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0x43fd3667…094b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa279b18d…63bc
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: Perpl
6 conflicts on slot 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity