← previous blocknext block →recent activity

Analyzing

Block #93,230,075

18 transactions · 16 stateful · 2026-08-05 02:40:29 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,230,075  ·  18 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

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0xfed09e59…a493

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x861e5aef…d32c

0x34b655…2a6f

4 touches
1 conflict

0x8f203394…f2db

0x34b655…2a6f

4 touches
1 conflict

0x8f203394…f2dc

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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: 0x40c49f17…d22af0

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity