← previous blocknext block →recent activity

Analyzing

Block #74,382,910

35 transactions · 29 stateful · 2026-05-13 19:24:53 UTC

Parallelism

80/100

Blocked

48%

Avg conflicts / tx

0.97

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,382,910  ·  35 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

0xf4c35608…fbc1

0xd32edf…ff58

13 touches
21 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0xf4c3560885…12fbc1

← previous block·next block →recent activity