← previous blocknext block →recent activity

Analyzing

Block #74,703,827

15 transactions · 13 stateful · 2026-05-15 07:09:48 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,703,827  ·  15 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

0xd2facdba…7a7e

0x34b655…2a6f

6 touches
3 conflicts

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x2fad73a1…ae09

0x34b655…2a6f

4 touches
1 conflict

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0x59c5f814…8c6a

0x34b655…2a6f

4 touches
1 conflict

0x83f3d320…fb59

0x34b655…2a6f

4 touches
1 conflict

0xcd393df7…21f9

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