← previous blocknext block →recent activity

Analyzing

Block #74,402,470

24 transactions · 19 stateful · 2026-05-13 21:35:08 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,402,470  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0x904fc3c0…00ec

0x34b655…2a6f

4 touches
1 conflict

0xa05dafe7…aff6

0x34b655…2a6f

4 touches
1 conflict

0xd5ad0af4…2387

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity