← previous blocknext block →recent activity

Analyzing

Block #74,773,086

41 transactions · 29 stateful · 2026-05-15 14:52:43 UTC

Parallelism

83/100

Blocked

69%

Avg conflicts / tx

1.07

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,773,086  ·  41 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

0x948d35cd…b1bb

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

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 0x948d35cd47…b7b1bb

← previous block·next block →recent activity