← previous blocknext block →recent activity
Analyzing
Block #93,360,139
26 transactions · 21 stateful · 2026-08-05 13:34:26 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,360,139 · 26 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
1w02w13w25w09w010w112w213w217w318w419w122w023w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3dcefc65…432c
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x812c3078…1dd7
0xd32edf…ff58
5 touches
3 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x3dcefc6589…5b432c
Audit this contract →
← previous block·next block →recent activity