← previous blocknext block →recent activity

Analyzing

Block #74,040,646

13 transactions · 12 stateful · 2026-05-12 05:28:06 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,040,646  ·  13 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

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xd26843e2…8cdc

0xd32edf…ff58

3 touches
1 conflict

0x139e052f…41fe

0x065c9d…c394

2 touches
0 conflicts

0x38220d33…37ef

0x065c9d…c394

2 touches
0 conflicts

0x4138a94f…2bd3

0x065c9d…c394

2 touches
0 conflicts

0x4e8625e8…617f

0x065c9d…c394

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

1 conflict on slot 0xdaca243a5e…09f9de

← previous block·next block →recent activity