← previous blocknext block →recent activity

Analyzing

Block #92,080,296

24 transactions · 21 stateful · 2026-08-01 02:14:46 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,080,296  ·  24 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

0x35a9f06c…7689

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xa56e54d0…2d39

0x34b655…2a6f

6 touches
3 conflicts

0x7b55198a…b946

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x82a8425b…bc33

0x34b655…2a6f

6 touches
3 conflicts

0x70b5d52d…3ea7

0x34b655…2a6f

4 touches
1 conflict

0x7422dfec…9118

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

15 conflicts on slot 0x35a9f06ccf…e37689

← previous block·next block →recent activity