← previous blocknext block →recent activity

Analyzing

Block #93,556,289

11 transactions · 9 stateful · 2026-08-06 06:00:32 UTC

Parallelism

64/100

Blocked

56%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,556,289  ·  11 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

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x9a8482cc…8bee

0x34b655…2a6f

4 touches
1 conflict

0x9c69390f…0832

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x4638d837…130f

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b77

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x07b86c51…cdae

0x2a68ba…90c5

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

1 conflict on slot 0x6d1b72eefe…416b78

← previous block·next block →recent activity