← previous blocknext block →recent activity

Analyzing

Block #74,770,307

26 transactions · 14 stateful · 2026-05-15 14:34:07 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,770,307  ·  26 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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x15007455…ed03

0x34b655…2a6f

4 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

4 touches
1 conflict

0x122acd34…18c4

0xd32edf…ff58

3 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0xb6ad672e…6325

0x065c9d…c394

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x7c403af1…31b1

0x3bd359…433a

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: 0x34b6552d…112a6f

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity