← previous blocknext block →recent activity

Analyzing

Block #74,515,187

38 transactions · 31 stateful · 2026-05-14 10:06:26 UTC

Parallelism

76/100

Blocked

48%

Avg conflicts / tx

1.37

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,515,187  ·  38 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x4d9fa732…2ad9

0xd32edf…ff58

17 touches
36 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

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

36 conflicts on slot 0x4d9fa7326a…442ad9

← previous block·next block →recent activity