← previous blocknext block →recent activity

Analyzing

Block #93,354,025

22 transactions · 20 stateful · 2026-08-05 13:03:42 UTC

Parallelism

50/100

Blocked

55%

Avg conflicts / tx

2.18

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #93,354,025  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xca841faa…486a

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

8 touches
6 conflicts

0xcffeac0d…2ddf

0x34b655…2a6f

8 touches
6 conflicts

0xd24f93ae…3667

0x34b655…2a6f

6 touches
3 conflicts

0x3d158563…8713

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

28 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity