← previous blocknext block →recent activity

Analyzing

Block #93,368,421

19 transactions · 18 stateful · 2026-08-05 14:16:04 UTC

Parallelism

89/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,368,421  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xe21c81f7…d19b

0x34b655…2a6f

4 touches
1 conflict

0x2c0fe9aa…dad9

0x34b655…2a6f

3 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

2 touches
0 conflicts

0x3939eef2…95ad

0x34b655…2a6f

2 touches
0 conflicts

0x47a10383…3e35

0x34b655…2a6f

2 touches
0 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

2 touches
0 conflicts

0x737acb78…fce8

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0xbde524f475…b143bf

← previous block·next block →recent activity