← previous blocknext block →recent activity
Analyzing
Block #93,328,523
31 transactions · 28 stateful · 2026-08-05 10:55:28 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
1.58
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #93,328,523 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w211w212w313w414w515w616w717w820w121w926w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65c5c2dc…cdde
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x2385516f…eca5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
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
21 conflicts on slot 0x65c5c2dca1…fccdde
Audit this contract →
← previous block·next block →recent activity