← previous blocknext block →recent activity

Analyzing

Block #92,452,944

16 transactions · 16 stateful · 2026-08-02 09:28:52 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,452,944  ·  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

0x02d79f72…b18e

0x34b655…2a6f

4 touches
1 conflict

0x1eb410fd…591d

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3a3b7b24…56ba

0x34b655…2a6f

4 touches
1 conflict

0x50d44a56…fe50

0x34b655…2a6f

4 touches
1 conflict

0x840d3ab7…c8c4

0x34b655…2a6f

4 touches
1 conflict

0x8eb21bd9…aa8b

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

1 conflict on slot 0x02d79f7285…53b18e

← previous block·next block →recent activity