← previous blocknext block →recent activity

Analyzing

Block #74,770,344

9 transactions · 8 stateful · 2026-05-15 14:34:22 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,770,344  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x688a5357…2cf0

0x065c9d…c394

4 touches
1 conflict

0x79d67338…ed27

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x96d0da54…8173

0x065c9d…c394

3 touches
1 conflict

0xbcc8cc1e…f252

0x065c9d…c394

3 touches
1 conflict

0x203604ef…cf5f

0x065c9d…c394

3 touches
1 conflict

0x9efbfa50…7883

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

1 conflict on slot 0xba38536db1…342b7d

← previous block·next block →recent activity