← previous blocknext block →recent activity

Analyzing

Block #93,438,590

22 transactions · 21 stateful · 2026-08-05 20:08:52 UTC

Parallelism

59/100

Blocked

52%

Avg conflicts / tx

1.45

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #93,438,590  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x7a2c83a3…a29a

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x7d3347d3…6fae

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xaa08b8fc…97b9

0x34b655…2a6f

6 touches
3 conflicts

0x574628e9…dcc3

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

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

21 conflicts on slot 0x7a2c83a30a…f3a29a

← previous block·next block →recent activity