← previous blocknext block →recent activity

Analyzing

Block #74,968,410

14 transactions · 13 stateful · 2026-05-16 12:37:20 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,968,410  ·  14 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

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x8aa1941d…2988

0x34b655…2a6f

4 touches
1 conflict

0xa29365a0…97c1

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

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: 0x34b6552d…112a6f

3 conflicts on slot 0x631b41138f…31baa9

← previous block·next block →recent activity