← previous blocknext block →recent activity
Analyzing
Block #93,369,142
25 transactions · 24 stateful · 2026-08-05 14:19:42 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,369,142 · 25 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
3w05w06w07w08w19w210w011w112w213w114w117w218w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa01f2285…f16f
0x34b655…2a6f
6 touches
3 conflicts
0xeb0ed9c8…5f39
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x2e7a0c1d…caaf
0x34b655…2a6f
4 touches
1 conflict
0x459323cd…b5ce
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity