← previous blocknext block →recent activity

Analyzing

Block #74,351,973

36 transactions · 17 stateful · 2026-05-13 15:58:57 UTC

Parallelism

89/100

Blocked

41%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,351,973  ·  36 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

0x5f8e513b…f2c9

0xd32edf…ff58

7 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x5593214e…dfc1

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x5e1b1a…7777

4 touches
1 conflict

0x4d1acd7c…f345

0x5e1b1a…7777

4 touches
1 conflict

0xffe004da…e2f4

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0x75c3ab…4f0d

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: 0xd32edf66…9fff58

6 conflicts on slot 0x5f8e513b74…8df2c9

← previous block·next block →recent activity