← previous blocknext block →recent activity

Analyzing

Block #93,368,346

24 transactions · 20 stateful · 2026-08-05 14:15:42 UTC

Parallelism

63/100

Blocked

55%

Avg conflicts / tx

1.46

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #93,368,346  ·  24 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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x41f1e2e5…2edf

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0x2c390858…b1ed

0x34b655…2a6f

10 touches
10 conflicts

0xb9ccd689…c424

0x34b655…2a6f

8 touches
6 conflicts

0x2bd4c467…ae85

0x34b655…2a6f

6 touches
3 conflicts

0x7eb8c313…837d

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 0xc824469a90…af6425

← previous block·next block →recent activity