← previous blocknext block →recent activity

Analyzing

Block #74,351,786

17 transactions · 13 stateful · 2026-05-13 15:57:42 UTC

Parallelism

76/100

Blocked

46%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,351,786  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x3673e95b…5b32

0xd32edf…ff58

7 touches
6 conflicts

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x5e13521a…8169

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0xd2b8cc8b…85fa

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: 0xd32edf66…9fff58

6 conflicts on slot 0x3673e95b84…915b32

← previous block·next block →recent activity