← previous blocknext block →recent activity

Analyzing

Block #93,345,231

16 transactions · 16 stateful · 2026-08-05 12:19:28 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,345,231  ·  16 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

0xfed09e59…a493

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf219f7cf…7379

0xa6afd3…d132

6 touches
3 conflicts

0x3f4f9f22…8ad6

0x34b655…2a6f

4 touches
1 conflict

0x3f4f9f22…8ad7

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x8299fe6c…5752

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 0xfed09e59c7…d6a493

← previous block·next block →recent activity