← previous blocknext block →recent activity
Analyzing
Block #93,672,902
19 transactions · 14 stateful · 2026-08-06 15:46:46 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,672,902 · 19 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
2w03w14w25w39w111w012w114w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98212952…9ba6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x13cd0705…ed56
0xd32edf…ff58
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xabf57eb6…416d
0x34b655…2a6f
6 touches
3 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
6 touches
3 conflicts
0x7d3347d3…6fae
0x34b655…2a6f
4 touches
1 conflict
0x84d2bf96…1eea
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 0x982129521c…f19ba6
Audit this contract →
← previous block·next block →recent activity