← previous blocknext block →recent activity

Analyzing

Block #92,756,897

7 transactions · 6 stateful · 2026-08-03 10:58:47 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641d

0x34b655…2a6f

4 touches
1 conflict

0x80398c66…f3cc

0x34b655…2a6f

4 touches
1 conflict

0x398674e0…2603

0x34b655…2a6f

4 touches
1 conflict

0x9a9383a9…6bc7

0x34b655…2a6f

4 touches
1 conflict

0x4bcbd0e7…5e26

0x34b655…2a6f

3 touches
1 conflict

0x7b41d5cd…00e6

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0xd66696e0dc…230842

← previous block·next block →recent activity