← previous blocknext block →recent activity

Analyzing

Block #74,390,344

13 transactions · 7 stateful · 2026-05-13 20:14:21 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,390,344  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xb258b731…cb94

0x065c9d…c394

3 touches
1 conflict

0xd3e71746…430f

0x065c9d…c394

3 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x1cf4426d…8753

0x065c9d…c394

2 touches
0 conflicts

0x1e3dc7bb…88b4

0x065c9d…c394

2 touches
0 conflicts

0x3a347a58…95e1

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity