← previous blocknext block →recent activity

Analyzing

Block #91,808,769

23 transactions · 22 stateful · 2026-07-31 03:28:54 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.96

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,808,769  ·  23 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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xe007ba13…37f9

0x34b655…2a6f

8 touches
6 conflicts

0x2fd12b6c…02cc

0x34b655…2a6f

6 touches
3 conflicts

0x3f4f9f22…8ad7

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x52b477bc…7ccf

0x34b655…2a6f

4 touches
1 conflict

0x6d955786…1327

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity