← previous blocknext block →recent activity

Analyzing

Block #74,389,853

40 transactions · 23 stateful · 2026-05-13 20:11:05 UTC

Parallelism

82/100

Blocked

43%

Avg conflicts / tx

0.72

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,389,853  ·  40 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

0x17606ba6…1b6e

0x754704…b603

14 touches
21 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x69f9a5c6…9354

0xd32edf…ff58

5 touches
3 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

4 touches
1 conflict

0xd31913b6…6e9a

0x754704…b603

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

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: 0x754704bc…afb603

21 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity