← previous blocknext block →recent activity

Analyzing

Block #93,339,222

24 transactions · 22 stateful · 2026-08-05 11:49:15 UTC

Parallelism

79/100

Blocked

36%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,339,222  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x861e5aef…d32c

0x34b655…2a6f

8 touches
6 conflicts

0xed59b1cd…8509

0x34b655…2a6f

6 touches
3 conflicts

0xe31e77c9…75d6

0x34b655…2a6f

6 touches
3 conflicts

0x4755fafb…859b

0x34b655…2a6f

6 touches
3 conflicts

0x65e6e603…cb45

0x34b655…2a6f

4 touches
1 conflict

0x6956d31b…6393

0x34b655…2a6f

4 touches
1 conflict

0x6989456e…7ae0

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x861e5aeffa…5cd32c

← previous block·next block →recent activity