← previous blocknext block →recent activity

Analyzing

Block #74,775,158

19 transactions · 14 stateful · 2026-05-15 15:06:35 UTC

Parallelism

79/100

Blocked

43%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,775,158  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x819a23fc…fa7d

0xd32edf…ff58

7 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x3efd1afc…bc58

0x065c9d…c394

3 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

2 touches
0 conflicts

0x1f101124…0069

0x188d58…ea8e

2 touches
0 conflicts

0x1f101124…006a

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

6 conflicts on slot 0x819a23fc84…53fa7d

← previous block·next block →recent activity