← previous blocknext block →recent activity

Analyzing

Block #93,591,391

23 transactions · 18 stateful · 2026-08-06 08:57:00 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

0.78

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,591,391  ·  23 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

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x7ea60711…6098

0x34b655…2a6f

6 touches
3 conflicts

0x80656e3b…9240

0x34b655…2a6f

6 touches
3 conflicts

0xe335efd4…1724

0x34b655…2a6f

5 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 0xbde524f475…b143bf

← previous block·next block →recent activity