← previous blocknext block →recent activity

Analyzing

Block #93,150,881

18 transactions · 17 stateful · 2026-08-04 20:02:19 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,150,881  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…00c9

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd392f9dc…0ae2

0x34b655…2a6f

6 touches
3 conflicts

0x9210e826…1414

0x34b655…2a6f

6 touches
3 conflicts

0x9a9383a9…6bc7

0x34b655…2a6f

6 touches
3 conflicts

0x9b2d3bee…8eeb

0x34b655…2a6f

6 touches
3 conflicts

0x092b7171…c16d

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

6 conflicts on slot 0x0000000000…0000c9

← previous block·next block →recent activity