← previous blocknext block →recent activity

Analyzing

Block #74,331,705

17 transactions · 12 stateful · 2026-05-13 13:44:14 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,331,705  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x2d8c9ff9…8b1d

0x34b655…2a6f

4 touches
1 conflict

0x993e5159…e99a

0x34b655…2a6f

4 touches
1 conflict

0x9a291a56…9a9c

0x34b655…2a6f

4 touches
1 conflict

0x041ee703…b4c1

0x34b655…2a6f

4 touches
1 conflict

0xb8228d38…3953

0x34b655…2a6f

4 touches
1 conflict

0xbb12db23…857e

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: 0x34b6552d…112a6f

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity