← previous blocknext block →recent activity

Analyzing

Block #92,648,312

21 transactions · 21 stateful · 2026-08-03 01:51:30 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,648,312  ·  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

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

10 touches
10 conflicts

0xd882b8cc…40eb

0x34b655…2a6f

6 touches
3 conflicts

0x3ad8bbeb…b084

0x34b655…2a6f

6 touches
3 conflicts

0xf8857df5…9a36

0x34b655…2a6f

5 touches
3 conflicts

0xce06a0f7…efef

0x34b655…2a6f

5 touches
3 conflicts

0x639eebcc…cff9

0x34b655…2a6f

5 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 0x737acb7813…fafce8

← previous block·next block →recent activity