← previous blocknext block →recent activity

Analyzing

Block #74,452,802

19 transactions · 12 stateful · 2026-05-14 03:10:08 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,452,802  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0xc53af6f0…50bd

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0x0175b7a6…1db9

0x5d823e…89c6

2 touches
0 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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity