← previous blocknext block →recent activity
Analyzing
Block #93,510,250
17 transactions · 17 stateful · 2026-08-06 02:09:07 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,510,250 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w17w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0xa279b18d…63bc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0x6bab0076…422b
0x34b655…2a6f
4 touches
1 conflict
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0xac8a5059…fd42
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 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity