← previous blocknext block →recent activity

Analyzing

Block #74,390,053

24 transactions · 21 stateful · 2026-05-13 20:12:25 UTC

Parallelism

75/100

Blocked

57%

Avg conflicts / tx

1.33

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,390,053  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x1c389468…6b0e

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x0fdbb550…7fdf

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x55d9e516…1ff1

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0xce8bbe33…b72e

0x3bd359…433a

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

10 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity