← previous blocknext block →recent activity

Analyzing

Block #74,774,327

25 transactions · 17 stateful · 2026-05-15 15:01:01 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,774,327  ·  25 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

0x3e49348b…9445

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xfd784183…67bb

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0x835675bb…b678

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

10 conflicts on slot 0x3e49348b38…839445

← previous block·next block →recent activity