← previous blocknext block →recent activity
Analyzing
Block #93,440,673
22 transactions · 22 stateful · 2026-08-05 20:19:20 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,440,673 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w08w19w210w211w312w415w516w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x99c5409a…25b7
0x34b655…2a6f
8 touches
6 conflicts
0x6bc8f55b…7d11
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xcce8f4b0…5e86
0x34b655…2a6f
8 touches
6 conflicts
0x69a45f39…39aa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
10 conflicts on slot 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity