← previous blocknext block →recent activity

Analyzing

Block #74,490,620

20 transactions · 18 stateful · 2026-05-14 07:21:49 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,490,620  ·  20 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

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x9fed9fec…7211

0x065c9d…c394

5 touches
3 conflicts

0xb88da7cd…07af

0x065c9d…c394

5 touches
3 conflicts

0x8a406265…34bb

0x065c9d…c394

5 touches
3 conflicts

0x45855fc6…68f6

0x065c9d…c394

5 touches
3 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

6 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity