← previous blocknext block →recent activity

Analyzing

Block #74,506,250

29 transactions · 22 stateful · 2026-05-14 09:06:13 UTC

Parallelism

76/100

Blocked

36%

Avg conflicts / tx

0.52

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,506,250  ·  29 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

0x0d0b2509…074d

0x3bd359…433a

10 touches
10 conflicts

0xe6455d1f…1029

0x754704…b603

10 touches
10 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

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: 0x3bd359c1…15433a

10 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity