← previous blocknext block →recent activity

Analyzing

Block #74,440,104

20 transactions · 14 stateful · 2026-05-14 01:45:38 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,440,104  ·  20 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

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xc83abe75…329d

0x34b655…2a6f

6 touches
3 conflicts

0xb42d40b2…0ad3

0xd32edf…ff58

5 touches
3 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x5f450515…3bc4

0x34b655…2a6f

4 touches
1 conflict

0x904fc3c0…00ec

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 0xf3981be56e…f02c47

← previous block·next block →recent activity