← previous blocknext block →recent activity

Analyzing

Block #74,326,293

27 transactions · 19 stateful · 2026-05-13 13:08:16 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,326,293  ·  27 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x2b9c6652…d14e

0x754704…b603

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity