← previous blocknext block →recent activity

Analyzing

Block #92,453,506

24 transactions · 23 stateful · 2026-08-02 09:31:42 UTC

Parallelism

83/100

Blocked

26%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,453,506  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x2e30c36b…b1fa

0x34b655…2a6f

6 touches
3 conflicts

0x0c7a4619…2b80

0x34b655…2a6f

4 touches
1 conflict

0x1eb410fd…591d

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x255bac2b…1b37

0x34b655…2a6f

4 touches
1 conflict

0x2ada3e8e…960f

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity