← previous blocknext block →recent activity

Analyzing

Block #74,359,784

4 transactions · 3 stateful · 2026-05-13 16:50:56 UTC

Parallelism

50/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,359,784  ·  4 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5675c293…17d9

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

4 touches
1 conflict

0x35019383…fc7d

0x34b655…2a6f

2 touches
0 conflicts

0x36f4b4f0…0188

0x34b655…2a6f

2 touches
0 conflicts

0x578e7f66…1b56

0x34b655…2a6f

2 touches
0 conflicts

0x5d70606a…1d53

0x34b655…2a6f

2 touches
0 conflicts

0x6c44331f…9735

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

1 conflict on slot 0x5675c29376…af17d9

← previous block·next block →recent activity