← previous blocknext block →recent activity

Analyzing

Block #74,428,660

22 transactions · 16 stateful · 2026-05-14 00:29:24 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,428,660  ·  22 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xb3e1599d…427d

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0001

0x116e7d…d8f1

4 touches
1 conflict

0x00000000…0003

0x116e7d…d8f1

4 touches
1 conflict

0xb7143610…adc4

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x116e7d…d8f1

4 touches
1 conflict

0x692a4122…76b8

0x350035…7777

4 touches
1 conflict

0x37852889…3d32

0x350035…7777

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity