← previous blocknext block →recent activity

Analyzing

Block #74,586,242

35 transactions · 24 stateful · 2026-05-14 18:04:49 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,586,242  ·  35 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

0xbad68552…e6bf

0x34b655…2a6f

10 touches
10 conflicts

0x29f2d148…a3eb

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xca0fef1c…b548

0x34b655…2a6f

6 touches
3 conflicts

0x06c10d86…6883

0x34b655…2a6f

4 touches
1 conflict

0x1279ee2d…ae99

0x34b655…2a6f

4 touches
1 conflict

0x157d1e46…85f6

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 0xbad6855239…f0e6bf

← previous block·next block →recent activity