← previous blocknext block →recent activity

Analyzing

Block #92,162,971

20 transactions · 18 stateful · 2026-08-01 09:10:35 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,162,971  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x177211e2…1c2d

0x754704…b603

6 touches
3 conflicts

0xe1f61186…e2f8

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x7b9256…1fb2

6 touches
3 conflicts

0x3174f37b…a5f2

0x7b9256…1fb2

6 touches
3 conflicts

0x3174f37b…a5f3

0x7b9256…1fb2

6 touches
3 conflicts

0x3174f37b…a5f6

0x7b9256…1fb2

6 touches
3 conflicts

0x6576ad40…546e

0x7b9256…1fb2

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity