← previous blocknext block →recent activity

Analyzing

Block #74,412,193

8 transactions · 8 stateful · 2026-05-13 22:39:51 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,412,193  ·  8 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

0x00f245ce…1e10

0x34b655…2a6f

6 touches
3 conflicts

0xb245fe36…d765

0x34b655…2a6f

6 touches
3 conflicts

0x5fad6fee…7714

0x34b655…2a6f

6 touches
3 conflicts

0x9b36f19f…fa5a

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x2fad73a1…ae09

0x34b655…2a6f

2 touches
0 conflicts

0x32a7b726…3633

0x34b655…2a6f

2 touches
0 conflicts

0x5c006808…f410

0x34b655…2a6f

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 0x00f245ce7e…641e10

← previous block·next block →recent activity