← previous blocknext block →recent activity

Analyzing

Block #74,511,157

26 transactions · 22 stateful · 2026-05-14 09:39:17 UTC

Parallelism

81/100

Blocked

55%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,511,157  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb8d98b10…4205

0xd32edf…ff58

9 touches
10 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x2b9c6652…d14e

0x754704…b603

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 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

10 conflicts on slot 0xb8d98b10b1…c84205

← previous block·next block →recent activity