← previous blocknext block →recent activity

Analyzing

Block #74,504,932

13 transactions · 11 stateful · 2026-05-14 08:57:19 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,504,932  ·  13 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

0xab621973…cc16

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x4b9553a7…3c4f

0x3bd359…433a

2 touches
1 conflict

0x45b9e08c…a11b

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

2 touches
0 conflicts

0x908d4442…2c4b

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 0xab621973ca…74cc16

← previous block·next block →recent activity