← previous blocknext block →recent activity
Analyzing
Block #93,664,481
11 transactions · 11 stateful · 2026-08-06 15:04:26 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,664,481 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4bbb6330…f81b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0x8488f10f…9353
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9354
0x2b46c0…1669
2 touches
0 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
6 conflicts on slot 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity