← previous blocknext block →recent activity

Analyzing

Block #74,765,436

28 transactions · 19 stateful · 2026-05-15 14:01:27 UTC

Parallelism

86/100

Blocked

26%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,765,436  ·  28 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xfc97b220…b278

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x00000000…0000

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0002

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0003

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…001b

0x116e7d…d8f1

2 touches
0 conflicts

0xab2f6eed…254a

0x188d58…ea8e

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: 0xd32edf66…9fff58

6 conflicts on slot 0xfc97b2209b…e6b278

← previous block·next block →recent activity