← previous blocknext block →recent activity

Analyzing

Block #93,672,220

25 transactions · 23 stateful · 2026-08-06 15:43:20 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,672,220  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x8743e1ba…8331

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xecf72a3c…67a3

0x34b655…2a6f

6 touches
3 conflicts

0x65bdc5fa…d7f3

0x34b655…2a6f

4 touches
1 conflict

0x72083f0d…082a

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd7

0x34b655…2a6f

4 touches
1 conflict

0xabffe139…e172

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 0x8743e1bab8…0a8331

← previous block·next block →recent activity