← previous blocknext block →recent activity

Analyzing

Block #74,342,848

23 transactions · 16 stateful · 2026-05-13 14:58:20 UTC

Parallelism

70/100

Blocked

63%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,342,848  ·  23 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

0xe6506724…3c79

0xd32edf…ff58

13 touches
21 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb8228d38…3953

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x72773122…2df8

0x065c9d…c394

2 touches
0 conflicts

0x4aa4f53b…899f

0x188d58…ea8e

2 touches
0 conflicts

0x4aa4f53b…89a1

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

21 conflicts on slot 0xe650672484…a03c79

← previous block·next block →recent activity