← previous blocknext block →recent activity

Analyzing

Block #74,352,026

24 transactions · 16 stateful · 2026-05-13 15:59:18 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,352,026  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0x2233f38c…0d84

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x22e0cc1d…ad04

0x34b655…2a6f

2 touches
0 conflicts

0x32454f9f…67d2

0x34b655…2a6f

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity