← previous blocknext block →recent activity

Analyzing

Block #74,613,287

42 transactions · 25 stateful · 2026-05-14 21:05:53 UTC

Parallelism

86/100

Blocked

60%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,613,287  ·  42 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00d0d8e3…ae88

0xd32edf…ff58

11 touches
15 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 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: 0xd32edf66…9fff58

15 conflicts on slot 0x00d0d8e3e4…88ae88

← previous block·next block →recent activity