← previous blocknext block →recent activity

Analyzing

Block #74,920,950

21 transactions · 17 stateful · 2026-05-16 07:19:09 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,920,950  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0x8c60ff10…5df7

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x457a4030…329e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

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: Perpl

6 conflicts on slot 0xb9868b5233…c6c77f

← previous block·next block →recent activity