← previous blocknext block →recent activity

Analyzing

Block #92,062,664

17 transactions · 16 stateful · 2026-08-01 00:46:05 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,062,664  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0006

0x7b9256…1fb2

10 touches
10 conflicts

0xe1f61186…e2f8

0x754704…b603

10 touches
10 conflicts

0x925617fc…d0a6

0x7b9256…1fb2

8 touches
6 conflicts

0x177211e2…1c2d

0x754704…b603

8 touches
6 conflicts

0x36ef9b65…26d1

0x7b9256…1fb2

8 touches
6 conflicts

0x925617fc…d0a5

0x7b9256…1fb2

8 touches
6 conflicts

0x36ef9b65…26cd

0x7b9256…1fb2

8 touches
6 conflicts

0x36ef9b65…26ce

0x7b9256…1fb2

8 touches
6 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: 0x7b9256fd…e21fb2

10 conflicts on slot 0x0000000000…000006

← previous block·next block →recent activity