← previous blocknext block →recent activity

Analyzing

Block #93,658,689

20 transactions · 19 stateful · 2026-08-06 14:35:19 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,658,689  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x6f3f704a…786d

0x34b655…2a6f

8 touches
6 conflicts

0xa279b18d…63bc

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xb6fcbbb7…2b31

0x34b655…2a6f

6 touches
3 conflicts

0x809f2ba8…89d3

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity