← previous blocknext block →recent activity

Analyzing

Block #92,790,310

22 transactions · 20 stateful · 2026-08-03 13:46:57 UTC

Parallelism

68/100

Blocked

40%

Avg conflicts / tx

0.64

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,790,310  ·  22 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

0x8a5ced1c…3b29

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xae8e160e…75a9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x81681867…64fa

0x34b655…2a6f

4 touches
1 conflict

0x94aff148…b584

0x34b655…2a6f

4 touches
1 conflict

0xbfd33a92…5c35

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 0x8a5ced1cae…443b29

← previous block·next block →recent activity