← previous blocknext block →recent activity

Analyzing

Block #93,922,287

18 transactions · 16 stateful · 2026-08-07 12:40:58 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,922,287  ·  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

0xbb322930…ace5

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0xdb5c3087…bf65

0x34b655…2a6f

4 touches
1 conflict

0xe8d58d34…426d

0x34b655…2a6f

4 touches
1 conflict

0xecb2b88e…24c8

0x34b655…2a6f

4 touches
1 conflict

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

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 0xbb32293008…46ace5

← previous block·next block →recent activity