← previous blocknext block →recent activity

Analyzing

Block #92,312,447

16 transactions · 15 stateful · 2026-08-01 21:42:20 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x033cf007…136d

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x177211e2…1c2d

0x754704…b603

6 touches
3 conflicts

0x4bc1abab…5874

0x34b655…2a6f

5 touches
3 conflicts

0xf8857df5…9a36

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…0006

0x7b9256…1fb2

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

3 conflicts on slot 0x033cf007c8…d2136d

← previous block·next block →recent activity