← previous blocknext block →recent activity

Analyzing

Block #74,805,405

17 transactions · 13 stateful · 2026-05-15 18:28:37 UTC

Parallelism

82/100

Blocked

23%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,805,405  ·  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

0x83c17cc9…7bc0

0xd32edf…ff58

5 touches
3 conflicts

0x47542f2a…be2d

0x065c9d…c394

4 touches
1 conflict

0x8a2f9a36…fb4a

0xfa32f9…f3f0

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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: 0xd32edf66…9fff58

3 conflicts on slot 0x83c17cc958…247bc0

← previous block·next block →recent activity