← previous blocknext block →recent activity

Analyzing

Block #74,415,190

25 transactions · 22 stateful · 2026-05-13 22:59:45 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.8

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,415,190  ·  25 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

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xa3ff1ab2…8ae3

0x34b655…2a6f

6 touches
3 conflicts

0x3e4b8d9f…b8a7

0x5d823e…89c6

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 0xffe431af56…838faa

← previous block·next block →recent activity