← previous blocknext block →recent activity

Analyzing

Block #74,649,025

15 transactions · 14 stateful · 2026-05-15 01:04:03 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,649,025  ·  15 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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x055c6b3d…1ccc

0x065c9d…c394

2 touches
0 conflicts

0x23d0d09a…183f

0x065c9d…c394

2 touches
0 conflicts

0x5475b36a…331a

0x065c9d…c394

2 touches
0 conflicts

0xd77a365a…f6f2

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

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