← previous blocknext block →recent activity
Analyzing
Block #93,401,123
26 transactions · 25 stateful · 2026-08-05 17:00:30 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,401,123 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w09w110w212w313w414w515w117w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fe37a3f…4c89
0x34b655…2a6f
8 touches
6 conflicts
0x428b6e5b…8909
0x34b655…2a6f
8 touches
6 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x3260d0da…4385
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
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 0x8fe37a3f4a…bf4c89
Audit this contract →
← previous block·next block →recent activity