← previous blocknext block →recent activity

Analyzing

Block #93,073,930

35 transactions · 28 stateful · 2026-08-04 13:34:29 UTC

Parallelism

77/100

Blocked

64%

Avg conflicts / tx

1.54

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,073,930  ·  35 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

0x00000000…0002

0x91855e…ac7e

16 touches
28 conflicts

0x889d5e90…929a

0x2a68ba…90c5

10 touches
10 conflicts

0x1a287886…0266

0xa6afd3…d132

8 touches
6 conflicts

0x1803586e…d149

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0xdb067026…9eb8

0x2b46c0…1669

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xb39cb1d8…effa

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: 0x91855e79…58ac7e

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity