← previous blocknext block →recent activity

Analyzing

Block #92,571,010

19 transactions · 17 stateful · 2026-08-02 19:22:41 UTC

Parallelism

68/100

Blocked

41%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,571,010  ·  19 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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x85971f5d…e920

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x9e308c47…d78d

0x34b655…2a6f

6 touches
3 conflicts

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x290b452a…59db

0x34b655…2a6f

4 touches
1 conflict

0x4327afd2…1b3a

0x34b655…2a6f

4 touches
1 conflict

0x6b778857…f22f

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity