← previous blocknext block →recent activity

Analyzing

Block #74,774,283

17 transactions · 14 stateful · 2026-05-15 15:00:43 UTC

Parallelism

82/100

Blocked

43%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,774,283  ·  17 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

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0xd53220ed…4736

0x1b6862…e19c

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x7e28e55c…d05c

0x754704…b603

4 touches
1 conflict

0xcce2fd99…a8eb

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x659bd0…a9da

4 touches
1 conflict

0x00000000…0002

0x659bd0…a9da

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

3 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity