← previous blocknext block →recent activity
Analyzing
Block #93,505,907
15 transactions · 15 stateful · 2026-08-06 01:47:17 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,505,907 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w36w49w011w512w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x1f1ac759…b8fb
0x34b655…2a6f
4 touches
1 conflict
0x2def1f88…9b98
0x34b655…2a6f
4 touches
1 conflict
0x3be6268b…1928
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8cd191b6…2397
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
15 conflicts on slot 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity