← previous blocknext block →recent activity

Analyzing

Block #74,774,820

18 transactions · 15 stateful · 2026-05-15 15:04:19 UTC

Parallelism

72/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,774,820  ·  18 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

0x348fda08…7e96

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf76fcdd2…b151

0xd32edf…ff58

5 touches
3 conflicts

0x624032c8…5430

0x065c9d…c394

4 touches
1 conflict

0x2e2214a9…fe0d

0x5d823e…89c6

4 touches
1 conflict

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x7c4f6c90…3ee2

0x065c9d…c394

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

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

6 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity