← previous blocknext block →recent activity
Analyzing
Block #92,861,970
21 transactions · 19 stateful · 2026-08-03 19:47:37 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,861,970 · 21 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
5w06w18w19w210w311w414w515w616w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x571d1c03…f3e1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
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 0x571d1c0348…0ff3e1
Audit this contract →
← previous block·next block →recent activity