← previous blocknext block →recent activity

Analyzing

Block #74,774,609

17 transactions · 13 stateful · 2026-05-15 15:02:53 UTC

Parallelism

88/100

Blocked

23%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,774,609  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0x2734e00b…9b4f

0x3bd359…433a

2 touches
0 conflicts

0xea9082f4…04a2

0x3bd359…433a

2 touches
0 conflicts

0x0175b7a6…1dba

0x5d823e…89c6

2 touches
0 conflicts

0x0175b7a6…1dbb

0x5d823e…89c6

2 touches
0 conflicts

0x2e2214a9…fe0d

0x5d823e…89c6

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity