← previous blocknext block →recent activity

Analyzing

Block #74,183,192

18 transactions · 16 stateful · 2026-05-12 21:16:36 UTC

Parallelism

78/100

Blocked

31%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,183,192  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x151c06b2…09e4

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x7299cbde…bdc2

0x065c9d…c394

3 touches
1 conflict

0x00280916…12f3

0xd32edf…ff58

3 touches
1 conflict

0x8792f9f3…60e5

0x065c9d…c394

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity