← previous blocknext block →recent activity

Analyzing

Block #74,473,005

23 transactions · 11 stateful · 2026-05-14 05:24:32 UTC

Parallelism

70/100

Blocked

55%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,473,005  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6bbd309a…dd38

0xd32edf…ff58

9 touches
10 conflicts

0x12309510…0ac2

0x000000…012a

8 touches
6 conflicts

0x33018431…8f5c

0x188d58…ea8e

8 touches
6 conflicts

0x33018431…8f5d

0x188d58…ea8e

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x2f77f0f6…4a93

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5f

0x188d58…ea8e

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

10 conflicts on slot 0x6bbd309a61…cddd38

← previous block·next block →recent activity