← previous blocknext block →recent activity

Analyzing

Block #93,352,059

26 transactions · 24 stateful · 2026-08-05 12:53:47 UTC

Parallelism

69/100

Blocked

38%

Avg conflicts / tx

1.15

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,352,059  ·  26 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

0xd66696e0…0842

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xe21a94dd…4838

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…641f

0x34b655…2a6f

8 touches
6 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

8 touches
6 conflicts

0x9cf9008a…d826

0x34b655…2a6f

7 touches
6 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 0xd66696e0dc…230842

← previous block·next block →recent activity