← previous blocknext block →recent activity

Analyzing

Block #93,401,354

20 transactions · 19 stateful · 2026-08-05 17:01:40 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

0.75

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,401,354  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xabd0bcfc…64e2

0x34b655…2a6f

6 touches
3 conflicts

0x2840c278…bbc7

0x34b655…2a6f

6 touches
3 conflicts

0x6847107a…f468

0xa6afd3…d132

6 touches
3 conflicts

0x2491d756…b71c

0xa6afd3…d132

6 touches
3 conflicts

0x9ba6ae4a…90cb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xec7d120d…7085

0x34b655…2a6f

4 touches
1 conflict

0xec7d120d…7084

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

3 conflicts on slot 0xabd0bcfc80…a364e2

← previous block·next block →recent activity