← previous blocknext block →recent activity

Analyzing

Block #74,627,250

17 transactions · 13 stateful · 2026-05-14 22:39:04 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,627,250  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfd784183…67bb

0x34b655…2a6f

4 touches
1 conflict

0xc5299629…5df0

0x065c9d…c394

3 touches
1 conflict

0x6518c685…7c09

0x065c9d…c394

2 touches
0 conflicts

0xce1a8e5b…5431

0x065c9d…c394

2 touches
0 conflicts

0xea4fbdc7…bd59

0x065c9d…c394

2 touches
0 conflicts

0xeaf4270f…92b0

0x065c9d…c394

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity