← previous blocknext block →recent activity

Analyzing

Block #93,076,159

24 transactions · 19 stateful · 2026-08-04 13:45:48 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,076,159  ·  24 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xc6289ade…f211

0x34b655…2a6f

6 touches
3 conflicts

0x033cf007…136d

0x34b655…2a6f

4 touches
1 conflict

0x28ceceef…ecc2

0x34b655…2a6f

4 touches
1 conflict

0x4bc1abab…5874

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0xc824469a90…af6425

← previous block·next block →recent activity