← previous blocknext block →recent activity

Analyzing

Block #74,351,870

37 transactions · 25 stateful · 2026-05-13 15:58:15 UTC

Parallelism

81/100

Blocked

52%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,351,870  ·  37 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

0xac0d9dff…e8a1

0xd32edf…ff58

9 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0x4e01a6b9…ed8e

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x904fc3c0…00ec

0x34b655…2a6f

4 touches
1 conflict

0xd2b8cc8b…85fa

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

10 conflicts on slot 0xac0d9dff26…92e8a1

← previous block·next block →recent activity