← previous blocknext block →recent activity

Analyzing

Block #74,287,162

17 transactions · 13 stateful · 2026-05-13 08:47:50 UTC

Parallelism

71/100

Blocked

46%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,287,162  ·  17 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

0x6218cdb8…0852

0x34b655…2a6f

8 touches
6 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd6aabe89…92f5

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x52717311…ae97

0x34b655…2a6f

4 touches
1 conflict

0x5d70606a…1d53

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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

6 conflicts on slot 0x6218cdb809…f80852

← previous block·next block →recent activity