← previous blocknext block →recent activity

Analyzing

Block #93,398,781

18 transactions · 16 stateful · 2026-08-05 16:48:43 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,398,781  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc6000ba5…8d65

0x34b655…2a6f

8 touches
6 conflicts

0x6629b7f2…c972

0x34b655…2a6f

6 touches
3 conflicts

0xf06fce24…887d

0x34b655…2a6f

6 touches
3 conflicts

0x1d9867ad…6d9a

0x34b655…2a6f

4 touches
1 conflict

0x2d651956…12e8

0x34b655…2a6f

4 touches
1 conflict

0x3f25409b…f92b

0x34b655…2a6f

4 touches
1 conflict

0x410b84ab…1dbc

0x34b655…2a6f

4 touches
1 conflict

0x46346c28…1297

0x34b655…2a6f

4 touches
1 conflict

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 0xc6000ba5c1…988d65

← previous block·next block →recent activity