← previous blocknext block →recent activity

Analyzing

Block #92,431,548

20 transactions · 18 stateful · 2026-08-02 07:41:16 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

0.85

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,431,548  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x39cf3627…6a7c

0x34b655…2a6f

8 touches
6 conflicts

0x03b16972…8f62

0x34b655…2a6f

6 touches
3 conflicts

0xb0563e8d…0662

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity