← previous blocknext block →recent activity
Analyzing
Block #93,501,558
20 transactions · 20 stateful · 2026-08-06 01:25:25 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,501,558 · 20 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
1w02w04w05w08w111w112w213w314w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa279b18d…63bc
0x34b655…2a6f
8 touches
6 conflicts
0xb1b58b33…874f
0x34b655…2a6f
6 touches
3 conflicts
0xa1ff0729…0146
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd4498307…88dc
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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
6 conflicts on slot 0xa279b18d93…8363bc
Audit this contract →
← previous block·next block →recent activity