← previous blocknext block →recent activity

Analyzing

Block #74,255,193

21 transactions · 17 stateful · 2026-05-13 05:15:21 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,255,193  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0x0e000224…1f1e

0xd32edf…ff58

3 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity