← previous blocknext block →recent activity

Analyzing

Block #74,306,631

17 transactions · 11 stateful · 2026-05-13 10:57:29 UTC

Parallelism

76/100

Blocked

36%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,306,631  ·  17 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

0xd29fbd52…f080

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x8d19e69f…22f9

0x699abc…6a3b

4 touches
1 conflict

0x33a51869…4642

0x699abc…6a3b

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x512f983e…0b0a

0xd32edf…ff58

3 touches
1 conflict

0x2fb6ddd2…b2a4

0x000000…012a

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

3 conflicts on slot 0xd29fbd52e2…66f080

← previous block·next block →recent activity