← previous blocknext block →recent activity

Analyzing

Block #93,577,058

22 transactions · 22 stateful · 2026-08-06 07:44:57 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,577,058  ·  22 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

0x52b477bc…7ccf

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xd6bd849a…5597

0x2a68ba…90c5

4 touches
1 conflict

0x40970e69…da50

0x2b46c0…1669

4 touches
1 conflict

0x8cf3d245…1d0d

0x2b46c0…1669

4 touches
1 conflict

0xb05cd4f5…73d0

0x2b46c0…1669

4 touches
1 conflict

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x3c5ea1e9…7e5a

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 0x52b477bcb8…5d7ccf

← previous block·next block →recent activity