← previous blocknext block →recent activity
Analyzing
Block #93,322,248
26 transactions · 26 stateful · 2026-08-05 10:23:55 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,322,248 · 26 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
3w05w06w08w111w113w218w019w123w224w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51d03c9d…57a7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x1cdf1b48…9f5e
0x34b655…2a6f
4 touches
1 conflict
0x6f97afda…faec
0x34b655…2a6f
4 touches
1 conflict
0xb13b96bd…a3cb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x51d03c9de0…c357a7
Audit this contract →
← previous block·next block →recent activity