← previous blocknext block →recent activity

Analyzing

Block #93,075,306

18 transactions · 16 stateful · 2026-08-04 13:41:29 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,075,306  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6b76d7a1…d19b

0x851145…3f07

6 touches
3 conflicts

0xa1bfcc4c…f2db

0x851145…3f07

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x76d1e78d…7877

0x40c49f…2af0

4 touches
1 conflict

0x234ec001…1b5a

0x40c49f…2af0

4 touches
1 conflict

0x1c912a68…3b21

0x2a68ba…90c5

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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: 0x851145ea…9f3f07

3 conflicts on slot 0x6b76d7a1a0…90d19b

← previous block·next block →recent activity