← previous blocknext block →recent activity

Analyzing

Block #92,569,775

21 transactions · 20 stateful · 2026-08-02 19:16:28 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,569,775  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd9331c2b…503c

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x620b761c…270e

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0x9a8af3c2…e4ae

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

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 0xd9331c2bba…40503c

← previous block·next block →recent activity