← previous blocknext block →recent activity

Analyzing

Block #74,502,112

26 transactions · 21 stateful · 2026-05-14 08:38:23 UTC

Parallelism

85/100

Blocked

43%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,502,112  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

4 touches
1 conflict

0x4381471a…9ac1

0x34b655…2a6f

4 touches
1 conflict

0x45b9e08c…a11b

0x34b655…2a6f

4 touches
1 conflict

0x5675c293…17d9

0x34b655…2a6f

4 touches
1 conflict

0x5d845038…9777

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity