← previous blocknext block →recent activity

Analyzing

Block #74,456,172

11 transactions · 7 stateful · 2026-05-14 03:32:38 UTC

Parallelism

73/100

Blocked

29%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,456,172  ·  11 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

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x2e4cef9a…1954

0x065c9d…c394

4 touches
1 conflict

0x1bd4950c…2445

0x0a3323…0a3c

2 touches
0 conflicts

0xb1632c2f…d991

0x0a3323…0a3c

2 touches
0 conflicts

0xff393f19…4dd2

0x0a3323…0a3c

2 touches
0 conflicts

0x00000000…0000

0x0d73bf…be07

2 touches
0 conflicts

0xfbad2c6c…0d32

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity