← previous blocknext block →recent activity

Analyzing

Block #74,775,636

34 transactions · 23 stateful · 2026-05-15 15:09:47 UTC

Parallelism

85/100

Blocked

39%

Avg conflicts / tx

0.38

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,775,636  ·  34 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x93afca4c…b47a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xf9be1f95…cc74

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

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

3 conflicts on slot 0xba38536db1…342b7d

← previous block·next block →recent activity