← previous blocknext block →recent activity

Analyzing

Block #74,231,586

13 transactions · 11 stateful · 2026-05-13 02:38:23 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,231,586  ·  13 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x479b9aee…3d03

0x065c9d…c394

2 touches
0 conflicts

0x7e1ed5d6…4abe

0x065c9d…c394

2 touches
0 conflicts

0x9d2bcb11…12b0

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity