← previous blocknext block →recent activity

Analyzing

Block #74,306,632

17 transactions · 13 stateful · 2026-05-13 10:57:30 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,306,632  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x56546e78…629d

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd75a2973…8af9

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity