← previous blocknext block →recent activity

Analyzing

Block #74,427,454

13 transactions · 12 stateful · 2026-05-14 00:21:21 UTC

Parallelism

77/100

Blocked

17%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,427,454  ·  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

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0x06c10d86…6883

0x34b655…2a6f

4 touches
1 conflict

0x2eaef64d…7f82

0x34b655…2a6f

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x06db03a6…4692

0x34b655…2a6f

2 touches
0 conflicts

0x0532f739…986a

0x699abc…6a3b

2 touches
0 conflicts

0x8847c634…0de2

0x699abc…6a3b

2 touches
0 conflicts

0xa1087a5c…66c4

0x754704…b603

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

3 conflicts on slot 0xbad6855239…f0e6bf

← previous block·next block →recent activity