← previous blocknext block →recent activity

Analyzing

Block #74,406,758

13 transactions · 11 stateful · 2026-05-13 22:03:41 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,406,758  ·  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

0xab621973…cc16

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe181f491…f4e3

0x34b655…2a6f

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0x194f2c02…19e6

0x2a68ba…90c5

2 touches
0 conflicts

0x17606ba6…1b6e

0x754704…b603

2 touches
0 conflicts

0x54336df6…66d4

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 0xab621973ca…74cc16

← previous block·next block →recent activity