← previous blocknext block →recent activity
Analyzing
Block #93,268,296
23 transactions · 20 stateful · 2026-08-05 05:52:39 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,268,296 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w28w312w113w414w015w117w220w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f484fd4…5288
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x772ab420…c2f6
0x34b655…2a6f
6 touches
3 conflicts
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
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
10 conflicts on slot 0x7f484fd4ae…145288
Audit this contract →
← previous block·next block →recent activity