← previous blocknext block →recent activity

Analyzing

Block #92,969,472

25 transactions · 22 stateful · 2026-08-04 04:48:27 UTC

Parallelism

72/100

Blocked

55%

Avg conflicts / tx

1.36

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,969,472  ·  25 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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xb9834665…e363

0x34b655…2a6f

8 touches
6 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

8 touches
6 conflicts

0x8eef368f…aa21

0x34b655…2a6f

8 touches
6 conflicts

0x6713b018…05f3

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x8f203394…f2db

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…7213

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity