← previous blocknext block →recent activity

Analyzing

Block #74,241,076

13 transactions · 11 stateful · 2026-05-13 03:41:29 UTC

Parallelism

69/100

Blocked

36%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,241,076  ·  13 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

0x8a35acfb…d1aa

0x8d66a4…3095

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0178c2de…b37d

0x8d66a4…3095

4 touches
1 conflict

0x0335ae80…8414

0x8d66a4…3095

4 touches
1 conflict

0x17cd1479…00bb

0x8d66a4…3095

4 touches
1 conflict

0x74825c4e…32e9

0x8d66a4…3095

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: 0x8d66a43f…113095

6 conflicts on slot 0x8a35acfbc1…6bd1aa

← previous block·next block →recent activity