← previous blocknext block →recent activity

Analyzing

Block #74,466,653

24 transactions · 14 stateful · 2026-05-14 04:42:24 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,466,653  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x6b319071…a105

0xc8689a…ee79

6 touches
3 conflicts

0x0175b7a6…1dba

0x5d823e…89c6

4 touches
1 conflict

0xf0f673fd…37a7

0x5d823e…89c6

3 touches
1 conflict

0x0ef1e663…8f2a

0x5d823e…89c6

3 touches
1 conflict

0x78fa393b…b4c2

0x065c9d…c394

3 touches
1 conflict

0xca77bfc6…5b70

0x065c9d…c394

3 touches
1 conflict

0xe7535190…5a0f

0x5d823e…89c6

3 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 0x0000000000…00003d

← previous block·next block →recent activity