← previous blocknext block →recent activity
Analyzing
Block #93,366,816
28 transactions · 27 stateful · 2026-08-05 14:08:00 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,366,816 · 28 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
1w02w13w04w15w26w38w29w314w315w417w318w521w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c390858…b1ed
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xf219f7cf…7379
0xa6afd3…d132
8 touches
6 conflicts
0x3464bbc5…a323
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
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 0x2c3908588c…50b1ed
Audit this contract →
← previous block·next block →recent activity