← previous blocknext block →recent activity

Analyzing

Block #93,657,254

23 transactions · 20 stateful · 2026-08-06 14:28:06 UTC

Parallelism

65/100

Blocked

55%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,657,254  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x231ccc13…a7c6

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x793aa64d…b09c

0x34b655…2a6f

6 touches
3 conflicts

0x913b59f3…c444

0x34b655…2a6f

6 touches
3 conflicts

0x9210e826…1414

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0x231ccc1338…7fa7c6

← previous block·next block →recent activity