← previous blocknext block →recent activity

Analyzing

Block #93,064,246

20 transactions · 18 stateful · 2026-08-04 12:45:25 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,064,246  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xb39cb1d8…effa

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x38bdc5d3…a632

0x34b655…2a6f

4 touches
1 conflict

0x41891af2…ed2a

0x34b655…2a6f

4 touches
1 conflict

0x70a2eb8e…ba35

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0xa3a621f8f3…6975a2

← previous block·next block →recent activity