← previous blocknext block →recent activity
Analyzing
Block #93,682,327
17 transactions · 14 stateful · 2026-08-06 16:34:09 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,682,327 · 17 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
3w04w15w27w28w310w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
10 touches
10 conflicts
0xc6b9bb4b…145a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xb5681617…e980
0x34b655…2a6f
6 touches
3 conflicts
0x7aae9795…06ed
0x34b655…2a6f
4 touches
1 conflict
0x7aae9795…06ee
0x34b655…2a6f
4 touches
1 conflict
0x4db733f6…c922
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
10 conflicts on slot 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity