← previous blocknext block →recent activity

Analyzing

Block #92,763,639

17 transactions · 17 stateful · 2026-08-03 11:32:44 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,763,639  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x81561f70…fefd

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0xaa6a7936…3f64

0x34b655…2a6f

5 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0e37797c…d724

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 0x81561f70ba…26fefd

← previous block·next block →recent activity