← previous blocknext block →recent activity
Analyzing
Block #93,682,226
19 transactions · 19 stateful · 2026-08-06 16:33:39 UTC
Parallelism
58/100
Blocked
37%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,682,226 · 19 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
1w02w03w14w25w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
10 touches
10 conflicts
0xc782a816…d172
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
6 touches
3 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc6f3fd4d…f042
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