← previous blocknext block →recent activity

Analyzing

Block #74,413,636

25 transactions · 19 stateful · 2026-05-13 22:49:28 UTC

Parallelism

68/100

Blocked

68%

Avg conflicts / tx

1.4

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,413,636  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x93ea54f7…c56e

0xd32edf…ff58

15 touches
28 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xd025d7d7…f05a

0x3bd359…433a

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x3e575f89…35bd

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: 0xd32edf66…9fff58

28 conflicts on slot 0x93ea54f7ab…cfc56e

← previous block·next block →recent activity