← previous blocknext block →recent activity

Analyzing

Block #74,218,495

34 transactions · 25 stateful · 2026-05-13 01:11:23 UTC

Parallelism

79/100

Blocked

64%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,218,495  ·  34 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xf823e97f…2ee6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity