← previous blocknext block →recent activity

Analyzing

Block #74,744,946

28 transactions · 17 stateful · 2026-05-15 11:44:11 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,744,946  ·  28 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

0x4b393da1…af52

0xd32edf…ff58

7 touches
6 conflicts

0xe90b7bce…c2e0

0xfa32f9…f3f0

4 touches
1 conflict

0xaeb5864c…7679

0x2a68ba…90c5

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x3b4f6ce5…12bc

0x40c49f…2af0

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x2b54cadb…4425

0xd18b7e…414b

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

6 conflicts on slot 0x4b393da177…5caf52

← previous block·next block →recent activity