← previous blocknext block →recent activity

Analyzing

Block #74,356,089

29 transactions · 18 stateful · 2026-05-13 16:26:22 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,356,089  ·  29 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

0x7f6703f0…3429

0xd32edf…ff58

15 touches
28 conflicts

0x2d7ebe6b…f30d

0x3bd359…433a

4 touches
1 conflict

0xa5451686…ca76

0x754704…b603

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0xbd45e74e…2216

0x000000…012a

2 touches
0 conflicts

0xb87ad4e7…7045

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

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

28 conflicts on slot 0x7f6703f02f…cf3429

← previous block·next block →recent activity