← previous blocknext block →recent activity

Analyzing

Block #92,309,872

20 transactions · 18 stateful · 2026-08-01 21:29:23 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,309,872  ·  20 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x07d94be1…7fa8

0x34b655…2a6f

6 touches
3 conflicts

0xe1f61186…e2f8

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x7b9256…1fb2

6 touches
3 conflicts

0x19fd6150…1124

0x7b9256…1fb2

6 touches
3 conflicts

0x19fd6150…1125

0x7b9256…1fb2

6 touches
3 conflicts

0x19fd6150…1128

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity