← previous blocknext block →recent activity

Analyzing

Block #74,346,161

20 transactions · 18 stateful · 2026-05-13 15:20:22 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,346,161  ·  20 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

6 touches
3 conflicts

0x313f2565…5b00

0x34b655…2a6f

4 touches
1 conflict

0x55888ede…6745

0x34b655…2a6f

4 touches
1 conflict

0x57de3828…3fbb

0x34b655…2a6f

4 touches
1 conflict

0x5d70606a…1d53

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x7b50a82b…f53d

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity