← previous blocknext block →recent activity

Analyzing

Block #74,772,390

36 transactions · 24 stateful · 2026-05-15 14:48:02 UTC

Parallelism

86/100

Blocked

46%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,772,390  ·  36 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x5841cd20…6e35

0xd32edf…ff58

7 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0xc1baef71…0689

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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

6 conflicts on slot 0x5841cd2025…8e6e35

← previous block·next block →recent activity