← previous blocknext block →recent activity

Analyzing

Block #92,559,782

18 transactions · 17 stateful · 2026-08-02 18:26:13 UTC

Parallelism

89/100

Blocked

12%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,559,782  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x85bfd0af…ce96

0x34b655…2a6f

4 touches
1 conflict

0xd4e08328…8567

0x34b655…2a6f

4 touches
1 conflict

0x213ee207…a151

0x2b46c0…1669

2 touches
0 conflicts

0x46279ae7…20dd

0x2b46c0…1669

2 touches
0 conflicts

0x53e50026…6d8c

0x2b46c0…1669

2 touches
0 conflicts

0x7f4a8466…f2cc

0x2b46c0…1669

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

1 conflict on slot 0x22e0cc1d4a…90ad04

← previous block·next block →recent activity