← previous blocknext block →recent activity

Analyzing

Block #74,981,159

15 transactions · 13 stateful · 2026-05-16 14:02:23 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,981,159  ·  15 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

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x85dde91b…3a0b

0x065c9d…c394

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x613f1be8…2f1e

0x34b655…2a6f

4 touches
1 conflict

0x7b6d2deb…dde0

0x34b655…2a6f

4 touches
1 conflict

0xc799e56d…45aa

0x34b655…2a6f

4 touches
1 conflict

0xca0fef1c…b548

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 0xb9868b5233…c6c77f

← previous block·next block →recent activity