← previous blocknext block →recent activity

Analyzing

Block #74,188,299

17 transactions · 14 stateful · 2026-05-12 21:50:30 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,188,299  ·  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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x499adbcf…eb20

0x34b655…2a6f

4 touches
1 conflict

0x51d607f1…6458

0x34b655…2a6f

4 touches
1 conflict

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x245a78ab…06b1

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity