← previous blocknext block →recent activity
Analyzing
Block #93,677,296
24 transactions · 20 stateful · 2026-08-06 16:08:52 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,677,296 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w39w210w312w114w416w217w522w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01889594…e1e5
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd676e291…3ecf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
4 touches
1 conflict
0x0a2131b3…455e
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 0x018895948f…b0e1e5
Audit this contract →
← previous block·next block →recent activity