← previous blocknext block →recent activity

Analyzing

Block #74,338,703

26 transactions · 14 stateful · 2026-05-13 14:30:48 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,338,703  ·  26 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

0x3305a7d5…c6bf

0xd32edf…ff58

9 touches
10 conflicts

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x694b052d…3904

0x34b655…2a6f

4 touches
1 conflict

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

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

10 conflicts on slot 0x3305a7d5e3…7ac6bf

← previous block·next block →recent activity