← previous blocknext block →recent activity

Analyzing

Block #91,778,897

16 transactions · 14 stateful · 2026-07-31 00:58:37 UTC

Parallelism

81/100

Blocked

14%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,778,897  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x31b39922…1e65

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x5b7f5a90…f4cd

0x34b655…2a6f

4 touches
1 conflict

0xc56b390b…e0ce

0x34b655…2a6f

3 touches
1 conflict

0xd19c9d38…b459

0x34b655…2a6f

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 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

3 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity