← previous blocknext block →recent activity

Analyzing

Block #74,486,888

16 transactions · 11 stateful · 2026-05-14 06:56:58 UTC

Parallelism

88/100

Blocked

9%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,486,888  ·  16 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

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x8a73ab92…2f47

0x065c9d…c394

2 touches
0 conflicts

0x9d2eee12…5885

0x065c9d…c394

2 touches
0 conflicts

0xb6b5d7f8…6b61

0x065c9d…c394

2 touches
0 conflicts

0xc6991cfa…d487

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: 0x34b6552d…112a6f

1 conflict on slot 0x28c180e141…a4f1e2

← previous block·next block →recent activity