← previous blocknext block →recent activity

Analyzing

Block #74,215,380

13 transactions · 12 stateful · 2026-05-13 00:50:37 UTC

Parallelism

62/100

Blocked

33%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,215,380  ·  13 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

0x537e2e5b…c3ab

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xb409e204…89ac

0x34b655…2a6f

6 touches
3 conflicts

0x17d87f0d…bfc5

0x34b655…2a6f

4 touches
1 conflict

0x0462262d…a368

0x34b655…2a6f

4 touches
1 conflict

0xefb236ca…f49b

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