← previous blocknext block →recent activity

Analyzing

Block #74,284,179

16 transactions · 14 stateful · 2026-05-13 08:28:02 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,284,179  ·  16 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0xd5a85f42…2b30

0x065c9d…c394

3 touches
1 conflict

0x20ff60ca…e329

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xf543f974…2ac0

0x065c9d…c394

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity