← previous blocknext block →recent activity
Analyzing
Block #92,810,097
34 transactions · 34 stateful · 2026-08-03 15:26:30 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
1.5
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #92,810,097 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w07w18w29w315w417w524w629w732w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x71bbf601…5874
0x34b655…2a6f
10 touches
10 conflicts
0xbc66586e…20fe
0x34b655…2a6f
8 touches
6 conflicts
0x0110331c…b891
0x34b655…2a6f
6 touches
3 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity