← previous blocknext block →recent activity
Analyzing
Block #93,658,362
18 transactions · 18 stateful · 2026-08-06 14:33:40 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,658,362 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w07w19w010w111w112w013w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4de96d1d…b043
0x34b655…2a6f
6 touches
3 conflicts
0xa1ff0729…0146
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1962b6a7…8526
0x851145…3f07
4 touches
1 conflict
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x4de96d1d85…07b043
Audit this contract →
← previous block·next block →recent activity