← previous blocknext block →recent activity

Analyzing

Block #74,196,888

11 transactions · 7 stateful · 2026-05-12 22:47:44 UTC

Parallelism

73/100

Blocked

29%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,196,888  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0x41629728…ee69

0x34b655…2a6f

3 touches
1 conflict

0x17d87f0d…bfc5

0x34b655…2a6f

2 touches
0 conflicts

0x2bf5cf4b…2f5b

0x34b655…2a6f

2 touches
0 conflicts

0x3e91bf83…a767

0x34b655…2a6f

2 touches
0 conflicts

0x44f26cbe…58c2

0x34b655…2a6f

2 touches
0 conflicts

0x482471ad…122f

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity