← previous blocknext block →recent activity

Analyzing

Block #74,644,235

36 transactions · 25 stateful · 2026-05-15 00:32:13 UTC

Parallelism

83/100

Blocked

56%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,644,235  ·  36 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

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

6 touches
3 conflicts

0xab2ed10a…0265

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

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: 0x34b6552d…112a6f

10 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity