← previous blocknext block →recent activity

Analyzing

Block #92,756,890

17 transactions · 16 stateful · 2026-08-03 10:58:45 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,756,890  ·  17 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

0xe5a9274d…78d7

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x15eb6170…3da3

0x34b655…2a6f

4 touches
1 conflict

0x207e9f25…4724

0x34b655…2a6f

4 touches
1 conflict

0x207e9f25…4725

0x34b655…2a6f

4 touches
1 conflict

0x6b564d99…b9eb

0x34b655…2a6f

4 touches
1 conflict

0x6b564d99…b9ec

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

6 conflicts on slot 0xe5a9274d87…0678d7

← previous block·next block →recent activity