← previous blocknext block →recent activity

Analyzing

Block #74,425,664

26 transactions · 21 stateful · 2026-05-14 00:09:29 UTC

Parallelism

81/100

Blocked

57%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,425,664  ·  26 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

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0x1c354dc0…96de

0x754704…b603

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0x0631de4a…90ec

0xd32edf…ff58

7 touches
6 conflicts

0x083a8763…5a7b

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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: 0x754704bc…afb603

6 conflicts on slot 0xf91b744ece…1a9117

← previous block·next block →recent activity