← previous blocknext block →recent activity

Analyzing

Block #74,596,518

31 transactions · 17 stateful · 2026-05-14 19:13:33 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.39

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,596,518  ·  31 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

0xd3627470…0dbe

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xffe004da…e2f4

0x754704…b603

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0xc5c4c1d1…2145

0x3bd359…433a

2 touches
0 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

2 touches
0 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

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

10 conflicts on slot 0xd362747011…1c0dbe

← previous block·next block →recent activity