← previous blocknext block →recent activity
Analyzing
Block #92,770,389
25 transactions · 25 stateful · 2026-08-03 12:06:42 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,770,389 · 25 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
4w06w07w18w112w213w115w316w217w318w420w021w122w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x326f2a00…a2a6
0x34b655…2a6f
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0xf4040809…c8fb
0x40c49f…2af0
4 touches
2 conflicts
0xcf827da3…f2a5
0x34b655…2a6f
4 touches
1 conflict
0xe08d161c…53fd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: 0x40c49f17…d22af0
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity