← previous blocknext block →recent activity

Analyzing

Block #93,370,534

25 transactions · 25 stateful · 2026-08-05 14:26:42 UTC

Parallelism

64/100

Blocked

52%

Avg conflicts / tx

1.8

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #93,370,534  ·  25 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

12 touches
15 conflicts

0xfecb18c0…01ed

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xdfc21d7c…e062

0x34b655…2a6f

10 touches
10 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

8 touches
6 conflicts

0x1a287886…0266

0xa6afd3…d132

6 touches
3 conflicts

0x231ccc13…a7c6

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

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

← previous block·next block →recent activity