← previous blocknext block →recent activity

Analyzing

Block #74,481,255

10 transactions · 8 stateful · 2026-05-14 06:19:28 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,481,255  ·  10 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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0a7bd8cc…5a12

0x699abc…6a3b

4 touches
1 conflict

0x54859b2f…e21c

0x699abc…6a3b

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x2f77f0f6…4a92

0x188d58…ea8e

2 touches
0 conflicts

0x2f77f0f6…4a93

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: 0x065c9d28…a9c394

3 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity