← previous blocknext block →recent activity
Analyzing
Block #93,556,236
22 transactions · 21 stateful · 2026-08-06 06:00:16 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,556,236 · 22 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
5w06w17w18w29w210w311w415w516w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c5409a…25b7
0x34b655…2a6f
10 touches
10 conflicts
0x69a45f39…39aa
0x34b655…2a6f
10 touches
10 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
8 touches
6 conflicts
0x938d4198…c359
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0x8218911e…3bed
0x34b655…2a6f
4 touches
1 conflict
0x9132c685…1821
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x99c5409a28…0025b7
Audit this contract →
← previous block·next block →recent activity