← previous blocknext block →recent activity
Analyzing
Block #93,291,329
29 transactions · 26 stateful · 2026-08-05 07:48:28 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
1.31
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #93,291,329 · 29 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w17w18w29w311w012w113w214w015w117w218w319w320w421w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x94de4d05…ad01
0x34b655…2a6f
8 touches
6 conflicts
0xa3791570…f07a
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x7b9f11c5…25f6
0xd32edf…ff58
7 touches
6 conflicts
0x639c3654…ffc2
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
15 conflicts on slot 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity