← previous blocknext block →recent activity

Analyzing

Block #92,870,365

14 transactions · 14 stateful · 2026-08-03 20:29:51 UTC

Parallelism

71/100

Blocked

29%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,870,365  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x75e74415…ba2d

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf4c9a0df…dcd4

0x34b655…2a6f

4 touches
1 conflict

0xf4c9a0df…dcd5

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x329f2f7d…dcff

0x34b655…2a6f

4 touches
1 conflict

0x53d526f9…1ab8

0x34b655…2a6f

4 touches
1 conflict

0x227f81ad…9165

0x34b655…2a6f

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 0x75e744154d…4fba2d

← previous block·next block →recent activity