← previous blocknext block →recent activity

Analyzing

Block #74,620,130

18 transactions · 10 stateful · 2026-05-14 21:51:34 UTC

Parallelism

83/100

Blocked

20%

Avg conflicts / tx

0.11

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,620,130  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x344c8f4b…c73d

0xd32edf…ff58

3 touches
1 conflict

0x62e20208…be65

0x0555e3…2b9c

2 touches
0 conflicts

0x8e80434a…a96d

0x0555e3…2b9c

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x2326e1bc…e29c

0x065c9d…c394

2 touches
0 conflicts

0xc75f2870…5089

0x065c9d…c394

2 touches
0 conflicts

0xe377ec40…0c30

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity