← previous blocknext block →recent activity

Analyzing

Block #74,346,333

13 transactions · 12 stateful · 2026-05-13 15:21:31 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,346,333  ·  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

0xce2b6650…ecc3

0x5c2513…7777

6 touches
3 conflicts

0x00000000…0000

0xcc67aa…c71c

6 touches
3 conflicts

0x00000000…0003

0xcc67aa…c71c

6 touches
3 conflicts

0x00c46468…f328

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0001

0xcc67aa…c71c

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x75f6889e…7f1e

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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: 0x5c2513cf…487777

3 conflicts on slot 0xce2b6650f3…b0ecc3

← previous block·next block →recent activity